Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,472
-
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.
-
customer priority3GitLab.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 priority4GitLab.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 priority5GitLab.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 priority6GitLab.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 priority7GitLab.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 priority8GitLab.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 priority9GitLab.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+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.
-
customer-collaborationGitLab.orgIssues for collaboration with customers specifically for issues under https://gitlab.com/gitlab-com/account-management
-
customer-retroGitLab.orgFor Support: Use to denote that an issue or merge request was opened as an action item from a Support ticket retrospective.