Customer facing vs. internal-only Issues/features

Is there a way to have customer-facing “Issues”, related to but separate from internal-only issues?  The goal is to have a private login for our customers to look at their list of issues, but only the issues that we want them to see.  

For example, my customer is asking for “make all the boxes talk to each other”, so I want to add that to a list that my customer can login and see.  Internally I need to make several issues related to this one: “add radio to schematic”, “update firmware to use radio”, etc… I don’t want my customer seeing the internal-only issues, or the source code.  A way to create a customer-facing road map, but with private per-customer login, would also be very useful.  Is this possible at the moment?  

You could probably do this through the GitHub API - but you’d need to build out your own website, etc.

Other than that, the only way I can think of would be to have a per-customer repo and only allow them access to that project — this would give you de-facto customer-only issues (you’d keep your internal issues on a separate repo entirely)

​If there’s anything else I can help you with, let me know; so happy to help further!

Kindest regards,

1 Like