Labels

Use this label to track any changes expected to have a meaningful impact on GitLab customers or the GitLab brand

This label is applied to Epics and Issues that must be prioritized above all other work for the Feb 10th launch, including the highest‑priority parallel work that must continue in support of DAP launch strategy

Note there's also a label with this name in the GitLab project

The Revenue Organization cannot sell DAP (the GitLab Credit SKU) without this capability to the customer that was referenced.

The Revenue Organization is able to sell or keep the customer referenced in comment, but the customer is expecting committed delivery on this capability for DAP

The Revenue Organization cannot renew DAP (the GitLab Credit SKU) without this capability with the customer that was referenced.

Group level label to track Cells related work for DBRE.

Label to track database headroom work for the DBRE team. This needs to be a group label in order to create issue boards, gitlab-org.

To track for Growth OKR gitlab-org/growth/product#1442

Issues related to authoring the .gitlab-ci.yml file and CI YAML configuration (https://docs.gitlab.com/ee/ci/yaml/) but excludes issues handled by another label such as "CI rules"

Issues related to Pipeline Directed Acyclic Graphs https://docs.gitlab.com/ee/ci/directed_acyclic_graph/

Analytics Engineering team that owns the data model transformations in Snowflake.

Data Consumer that builds a dashboard or analysis off curated data.