Labels
Prioritized labels 1
Drag to reorder prioritized labels and change their relative priority.
-
groupscalabilityGitLab.comPlatform Infrastructure Scalability group https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability
Labels 3,988
-
Cloud SpendGitLab.comIssues related to cloud provider usage fees, and particularly reducing cloud spend
-
CloudBlue Integration - IncidentGitLab.comAn unplanned interruption or reduction in the quality of the CloudBlue Integration.
-
Cloudflare UI ChangeGitLab.com / GitLab Infrastructure TeamUsed when an issue necessitates a manual change in the Cloudflare UI, for auditing purposes
-
Code contributor programGitLab.comProgram to support wider community contribution of code, issues, and translations
-
Commercial Sales PriorityGitLab.comUsed to denote an issue which will impact Commercial customers. Typically added if repeatedly seen by the Commercial Sales team.
-
Commercial Sales Priority1GitLab.comFor Commercial Sales<>Product: ONLY Commercial DRIs should apply this label to an issue or epic to identify it as a top priority from Commercial Sales. No more than 10 open issues and epics should have this priority at any time. See https://about.gitlab.com/handbook/sales/commercial/managing_product_issues.html
-
Commercial Sales Priority2GitLab.comFor Commercial Sales<>Product: ONLY Commercial DRIs should apply this label to an issue or epic to identify it as a "next" priority from Commercial Sales. No more than 10 open issues and epics should have this priority at any time. See https://about.gitlab.com/handbook/sales/commercial/managing_product_issues.html
-
Commercial Sales Priority3GitLab.comFor Commercial Sales<>Product: ONLY Commercial DRIs should apply this label to an issue or epic to identify it as a lower priority from Commercial Sales. There is no limit to the number of open issues and epics that should have this priority at any time. See https://about.gitlab.com/handbook/sales/commercial/managing_product_issues.html
-
Community InterestGitLab.comUse 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