Restrict an Issue or Epic to Selected Users
Release notes
Currently, there is no way to restrict users at any level from a specific issue or epic within a project. In order to protect an internal issue (beyond marking it confidential to outside viewers), one must create a separate, external project and invite those selected users to that project. This can be problematic as it can limit an Ultimate or Premium user's functionality if they are forced to stand up a free project to protect their information, which defeats the point of the security features of Ultimate. It also makes overall collaboration in general more difficult.
The solution would allow an issue/epic creator to restrict the ability to see or edit the issue with permissions like a Google doc does. It would allow one to specifically add/invite a user to collaborate in the issue/epic. It would also enable the issue creator to select who can/cannot add additional users to the issue/epic.
Problem to solve
The problem is the lack of the ability to create internal issue/epic-level confidentiality.
Proposal
- On the issue sidebar, the issue creator would have the option to edit/turn on an "Restricted Issue" option. Once activated, the creator would then assign or @ mention the appropriate users who need to collaborate on the issue.
- By default, only the creator could add a user; however, there should be an option to allow/assign others to do so.
Intended users
Unknown--conceivably could be used by all issue/epic creators.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
- Cameron (Compliance Manager)
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Presley (Product Designer)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Rachel (Release Manager)
- Alex (Security Operations Engineer)
- Simone (Software Engineer in Test)
- Allison (Application Ops)
- Priyanka (Platform Engineer)
- Dana (Data Analyst)
- Eddie (Content Editor)
-->
Feature Usage Metrics
Usage should be measured by the number of issues/epics that turn on this feature.
Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md
-->
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.