Private Epics and Roadmap in public project

Problem to solve

Similar as you can do for projects: have a project that is public, but not all its features.

Target audience

• Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker

• Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney

Further details

This is esp. useful for organisations on GitLab.com that want a single top level group (e.g. mine is remote-com) AND make use of epics AND have public / OS projects BUT don't want to make everything public when using epics.

I.e. any modern organisation that wants to use epics.

Proposal

Allow toggling the permissions for epics and roadmap (and potentially other features) on group level, like you can for projects.

What does success look like, and how can we measure that?

Success: More people on Ultimate on GitLab.com

Acceptance: My epics are hidden.

What is the type of buyer?

Ultimate, regards epics.

Links / references