Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
StretchGitLab.orgIssues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.
-
coach will finishGitLab.orgCommunity contributions that have stalled, and need to be picked up by a merge request coach: https://about.gitlab.com/job-families/expert/merge-request-coach
-
Next Patch ReleaseGitLab.orgIssues to put in the next patch release. Work on these first, and add the Pick Into Stable label to the merge request, along with the appropriate milestone.
-
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
-
customer+GitLab.orgFeatures and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
-
requires production accessGitLab.orgBugs that result in support having to access the production Rails console or filesystem to fix.
-
[deprecated] Accepting merge requestsGitLab.org[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
-
UXGitLab.orgIssues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.
-
Community contributionGitLab.orgIssues that have been scheduled for an upcoming release and are actively being worked on by our community
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
-
Lock on merge
- Issues
- Merge requests
- Epics
-
-
Plan [DEPRECATED]GitLab.orgPlease use the devops::plan label instead of this deprecated label. It is kept for historical issues.
Prioritized