Disallow Label Creation at the Project Level
Release notes
Problem to solve
The cascading nature of labels can make it extremely difficult for large teams with a lot of projects to know where labels are created and managed. Users need some way of preventing labels from being created in too many locations, while still allowing developers to write code.
Intended users
Metrics
Keep track to see how many projects turn of labels at the project level (relying solely instead on Group Labels)
User experience goal
Users ought to still use labels, but label management can be setup to only be at the group level and not the project level.
- When users navigate Project Settings > Visibility, project settings, features, they'll see a toggle for Labels
- When users hover over Project Information, the "Labels" tab is missing
- When users attempt to add/view labels via the API, it returns with an error stating that Labels are disabled
Proposal
Idea: Add a toggle in the Project Settings to turn on/off Label Management while still inheriting labels from the group level(s).
Further details
This is a simplest change to allow Developers to be able to contribute to codebases (projects) without ever being able to create/modify labels.
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
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.