Labels

Related to the Charts components built on gitlab-ui

Issues related to the registry cleanup policies https://docs.gitlab.com/ee/user/packages/container_registry/reduce_container_registry_storage.html

Temporary label to measure the number of issues/epics closed as a result of shipping the new epics experience. Label DRI @amandarueda

Related to the Self-Managed activation method of cloud licensing. Owned by `group::provision`.

Issues related to cloud provider usage fees, and particularly reducing cloud spend

DEPRECATED do not use. Use `Contributor Success`

Issue that still need triage for the Code Review FY23-Q3 OKR: create-stage#13033

Issue that have been triaged for the Code Review FY23-Q3 OKR: create-stage#13033

Shows currently planned Code Suggestions issues for https://gitlab.com/groups/gitlab-org/-/epics/10670

MRs that originated from a CodeChallenge.dev user

Changes to .gitlab/CODEOWNERS

This is a "must have" item for our release to GA

This is a "should have" item for our release to GA

This is a "nice to have" for our release to GA

Used to denote an issue which will impact Commercial customers. Typically added if repeatedly seen by the Commercial Sales team.

The sole purpose of this label is to communicate common bugs that the Provision Team have identified. This could probably be replaced by a more complex search using a combination of type::bug, priority::1, etc. when &291 is completed

Use this label to alert the Community Relations team of any changes expected to have a meaningful impact on the wider GitLab community or the GitLab brand