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
-
DataSecConsultGitLab.orgThis label indicates DataSec is doing some kind of miscellaneous work with this issue (i.e., consultative work at the request of another team that isn't spawning its own issue in our board).
-
Database EngineeringGitLab.orgPertaining database engineering concepts, patterns, improvements, etc.
-
Deferred UXGitLab.orgA follow-up issue for when we choose to deviate from the MVC, during implementation, in a way that harms the user experience. https://about.gitlab.com/handbook/engineering/workflow/#deferred-ux
-
Description templates (.gitlab/*)GitLab.orgCreate and update issue and MR templates in `.gitlab/*` (dev guidelines)
-
Design Priority1GitLab.orgUse this label when you want to mark the priority of a design issue as the top priority (i.e. do this first as the top priority 1) where you're expecting to deliver it at a 100% by the defined due date.
-
Design Priority2GitLab.orgUse this label when you want to mark the priority of a design issue as the second most important priority (i.e. do this second as the next priority 2) where you're expecting to deliver it at 80% by the defined due date.
-
Design Priority3GitLab.orgUse this label when you want to mark the priority of a design issue as the third-highest priority (i.e. do this third as the medium priority 3) where you're expecting to deliver it at 60% by the defined due date.
-
Design Priority4GitLab.orgUse this label when you want to mark the priority of a design issue as the fourth-highest priority (i.e. do this later as a lower priority 4) where you're expecting to deliver it at 40% by the defined due date.
-
Design Priority5GitLab.orgUse this label when you want to mark the priority of a design issue as the fifth-highest priority (i.e. do this later as a lower priority 5) where you're expecting to deliver it at 20% by the defined due date.
-
Design Priority6GitLab.orgUse this label when you want to mark the priority of a design issue as the sixth-highest priority (i.e. do this last as the least priority 6) where you're expecting to deliver it at 10% by the defined due date.