Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Sub-DepartmentOpsGitLab.comOps Sub-Department within Development https://about.gitlab.com/handbook/engineering/development/ops/
-
Sub-DepartmentSaaS PlatformsGitLab.comLabel for the Platforms: https://about.gitlab.com/handbook/engineering/infrastructure/platforms/
-
Sub-DepartmentSecComp Dedicated MarketsGitLab.comLabel used to denote work belonging to the Security Compliance - Dedicated Markets team https://about.gitlab.com/handbook/security/security-assurance/dedicated-compliance/
-
Sub-DepartmentTest PlatformGitLab.comLabel for the Test Platform Sub-Department: https://about.gitlab.com/handbook/engineering/quality/quality-engineering/
-
Support EfficiencyGitLab.comFor MRs that improve GitLab Support Team's efficiency (same as for gitlab-org)
-
Support PriorityGitLab.comUsed to denote an issue which will reduce ticket volume significantly. Typically added if repeatedly seen in customer tickets, and internally, by the Support team. EXCEPT IN L&R SUPPORT: For Fulfillment, apply this label to indicate an item of interest to L&R Support.
-
Support Priority1GitLab.comFor Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a top priority from Support. No more than 10 open issues and epics should have this priority at any time. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support Priority2GitLab.comFor Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as next in line after the Top 10 items from Support. No more than 10 open issues and epics should have this priority at any time. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support Priority3GitLab.comFor Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a lower priority item on Support's Issue List for Fulfillment. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support Priority4GitLab.comFor Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a low priority item on Support's Issue List for Fulfillment. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support PriorityCategorizeGitLab.comFor Support<>Fulfillment: Used when initially identifying a new or existing issue or epic as one to be included in Support's Issue List for Fulfillment. This identifies the item as needing to be categorized. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
Prioritized