Labels
Prioritized labels 6
Drag to reorder prioritized labels and change their relative priority.
-
Eng MetricsGeneralGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization
-
Eng MetricsEng DivisionGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization
-
Eng MetricsDevelopment DepartmentGitLab.com / GitLab Infrastructure Team / Cloud Cost UtilizationAnalytics support for Development Department
-
Eng MetricsInfrastructure DepartmentGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization
-
Eng MetricsQuality DepartmentGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization
-
Eng MetricsSecurity DepartmentGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization
Labels 3,995
-
Strategic UX BacklogGitLab.comThis label is applied to all epics and issues related to the Strategic UX Backlog.
-
Sub-DepartmentOpsGitLab.comOps Sub-Department within Development https://about.gitlab.com/handbook/engineering/development/ops/
-
Support DepartmentGitLab.com / GitLab Infrastructure Team / Cloud Cost Utilization / team-tasks
-
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