Optionally require membership to view epics
Release notes
Problem to solve
Today, project membership allows users to see epics in parent groups. Security-minded organizations may not want project members to be able to view epics in parent groups since they contain sensitive data.
An example: In some organizations, third-party contractors need access to just the information in the project to they are added. Marking all epics as confidential is cumbersome and error-prone. It also introduces complexity since marking an epic confidential will require all child epics, issues, and merge requests to be confidential too.
Proposal
- Provide a configuration option to prevent epics from being viewable without group membership.
- References to epics should be redacted. An example of where this is done well is in Slack when linked to a private room.
Intended users
Feature Usage Metrics
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.