Labels

Issues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.

Used by contributors that are currently students at an educational institution

We allow development to fix small problems they see in the code base without an issue that are incremental improvements. Tag issues/merge requests for work in this area.

Issues and MRs that improve GitLab Support Team's efficiency (same as for gitlab-com). This label gets added typically when an issue comes up multiple times. For Fulfillment, use scoped labels.

Used by GitLab Support to indicate an issue or epic of interest to them except in Fulfillment (use scoped labels)

Used 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.

For 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For 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://handbook.gitlab.com/handbook/support/license-and-renewals/workflows/managing_product_issues/

For 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/

L&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)

For 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/

Used to track MRs made by members of the Support Team to GitLab code or documentation

Show assigned support engineer interest or involvement

Issues related to integration with TFS (Microsoft Team Foundation Server)

Threat Intelligence recommendation related to public and/or customer communications.