Labels

Issues related to importing repositories from GitLab or external systems

Instance-level, Group-level or Built-in Project Templates

Used to label features that are in Beta https://docs.gitlab.com/ee/policy/alpha-beta-support.html#beta

Used to label features that are Experimental (https://docs.gitlab.com/ee/policy/alpha-beta-support.html#experiment)

Used to label features that are moving to General Availability https://docs.gitlab.com/ee/policy/alpha-beta-support.html#generally-available-ga

Introduced as part of the incident issue creation for a failed provision (https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5254).

This tag tracks professional services fixes across GitLab

Tracks resolved vulnerability issues that may be disclosed.

This merge request will be published in a self-managed GitLab release. This label is added using the Release Tools project, and should not be manually added to merge requests.

not aligned to strategy but business necessary: https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes

https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes

https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes

https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes

Determining what strategy this body of work falls into: https://about.gitlab.com/direction/fulfillment/purchase/#vision-mission-strategy-and-outcomes

Maintenance issues for group::purchase in the Billable Members category

Issue has gone through Quad Planning process (PM,Dev,UX,QE) and has recommendations from Quality Engineering