Labels
Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
-
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.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 3,663
-
Code Review FY23-Q3 OKRtriagedGitLab.orgIssue that have been triaged for the Code Review FY23-Q3 OKR: create-stage#13033
-
Code Suggestions PlannedGitLab.orgShows currently planned Code Suggestions issues for https://gitlab.com/groups/gitlab-org/-/epics/10670
-
Commercial Sales PriorityGitLab.orgUsed to denote an issue which will impact Commercial customers. Typically added if repeatedly seen by the Commercial Sales team.
-
Common Provisioning BugsGitLab.orgThe sole purpose of this label is to communicate common bugs that the Provision Team have identified. This could probably be replaced by a more complex search using a combination of type::bug, priority::1, etc. when &291 is completed
-
Community InterestGitLab.orgUse this label to alert the Community Relations team of any changes expected to have a meaningful impact on the wider GitLab community or the GitLab brand
-
Community ProgramsGitLab.orgIssues related to complimentary subscriptions to GitLab Ultimate for program participants.
-
Community challengeGitLab.orgKey issues to highlight for the wider community. Community members will receive a GitLab merchandise when an MR is merged.
-
Community contributionGitLab.orgIssues that have been scheduled for an upcoming release and are actively being worked on by our community
-
ConfidenceHighGitLab.orgRICE Framework - confidence is 100%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework
-
ConfidenceLowGitLab.orgRICE Framework - confidence is 50%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework
-
ConfidenceMediumGitLab.orgRICE Framework - confidence is 80%. https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework
-
Container Registry MigrationGitLab.orgIssues related with the Container Registry upgrade/migration (&5523)