Labels

This label signifies work that we are preparing as a candidate for an upcoming Quarterly plan. While in `scoping` we are ensuring the goal of the work, the usability expectations, what's included and not included are clear so that engineering can provide an estimate/feasibility of the work in the upcoming quarter.

Issues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it

Changes to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com

Issues that block the deployment to production

Used to identify all issues and epics related to the Cloud Sync Program

Issues generally related to projects.

Issues related to creating projects.

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