Flexible Permissions for issues (by label)
Description
We are managing big projects in GitLab where each project has many stakeholders that should see only issues regarding their area of interest (their domain, department) within the particular project.
The most flexible way to define an area of interest to an issue is adding a label, hence restricting access to an individual or a group by label would make sense.
At the moment we have are creating dedicated projects only for issues regarding a specific scope. This allows us to restrict access, but we are outside of the actual project the issues are about which makes e.g. referencing issues in commits problematic.
Speaking generally: In situations where collaboration demands hiding sensitive information or showing only relevant information within the scope of a project, finegrained permission management is necessary.
Proposal
- restrict visibility of issues by label (to users or groups)
- issues-only access for users/groups