Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,556
-
Support PriorityReviewGitLab.orgFor 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/
-
Support PriorityScoredGitLab.orgL&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.orgFor 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/
-
Support Team ContributionsGitLab.orgUsed to track MRs made by members of the Support Team to GitLab code or documentation
-
Support cases overviewGitLab.org / ci-cdShowcases of interesting/relevant support tickets from the Support Stable Counterpart
-
TIRecCommsGitLab.orgThreat Intelligence recommendation related to public and/or customer communications.
-
TIRecHuntingGitLab.orgThreat Intelligence recommendation related to hunting for traces of malicious activity.
-
TW-DRILysanneGitLab.orgEpics, issues, and MRs that are driven by or require input from the specified Technical Writer.
-
TW-DRIMarcelGitLab.orgEpics, issues, and MRs that are driven by or require input from the specified Technical Writer.