Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Support PriorityReviewGitLab.comFor Support<>Fulfillment: Use to indicate that the issue or epic on Support's Issue List for Fulfillment needs to be reviewed for possible reprioritization. Comment on the issue or epic outlining how you think it should be prioritized and your reasoning. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support PriorityScoredGitLab.comL&R Support uses this label as part of its monthly review of issues and epics to be prioritized (see https://gitlab.com/gitlab-com/support/licensing-subscription/fulfillment-requests/-/blob/main/.gitlab/issue_templates/monthly_prioritization.md)
-
Support PrioritySee EpicGitLab.comFor Support<>Fulfillment: ONLY L&R Support DRIs should apply this label to an issue or epic to identify it as a child of a prioritized epic on Support's Issue List for Fulfillment. See https://about.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues.html
-
Support-Ops-CategoryAccount DeletionsGitLab.comFor Account Deletions where SupportOps was involved
-
Support-Ops-PriorityHighGitLab.comHigh business impact. Needs action by the Support Ops team within 1 - 2 weeks.
-
Support-Ops-PriorityNormalGitLab.comNeeds action by the Support Ops team within the coming month/quarter/90 days
-
Support-Ops-Project-StagePlanGitLab.comIdentify a timeframe for the deliverable of the project, establish a baseline/benchmark and performance measures. Define roles and responsibilities.
-
SupportInterestGitLab.comThis label denotes that the implementation of an issue or EPIC is of interest to the GItLab Support Team
Prioritized