Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,510
- 
creator-pairingGitLab.orgIssues created during creator-pairing program. See #creator-pairing slack channel or ping @dzaporozhets
 - 
critical-customer-escalationGitLab.orgCustomer bugs that are escalated involving CS / TAM / Quality leadership
 - 
cross-groupGitLab.orgDenotes the issue belongs to another Group (or even Stage) but is being worked by a different Group's engineering team.
 - 
custom statusmust haveGitLab.orgIndicates that this item is required for Project Management's Q2 investment commitment
 - 
custom statusnice to haveGitLab.orgIndicates that this item is not required, but nice to have for Project Managements's Q2 investment commitment
 - 
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
 - 
customer priority1GitLab.orgUsed to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
 - 
customer priority10GitLab.orgUsed to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
 - 
customer priority2GitLab.orgUsed to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.