Labels

Used to track product qualified lead related work, as described in the Growth direction handbook page https://about.gitlab.com/direction/growth/#theme-2-build-out-pql-programs-to-become-a-scalable-and-effective-leads-source

Used to track work done by PSIRT

Issues relating to the Platform-as-a-Service product category

Backlog issues for Package Hunter and Package Hunter CLI

Issues in development for Package Hunter and Package Hunter CLI

Issues in planning for Package Hunter and Package Hunter CLI

Features that apply to all package repositories

Priority 1 issues for the Package Stage

Priority 2 issues for the Package stage

Issue label for cross-functional issues for the package team

Issues related to GitLab's Design System "Pajamas"

For design system contributions that are foundational, broadly applicable, and fully maintained by the Design System team.

For design system contributions that are reusable in several contexts but aren't system-wide standards.

For design system contributions that do not have enough information to make a clear decision on it's classification into the core or extended layer. that are foundational, broadly applicable, and fully maintained by the Design System team.

Used for MRs created as part of Pajamas Migration Day

The contributor leads execution while the Design System team provides feedback, advice, and review. This is the default level of support for contributions to the core layer.

End-to-end: the Design System team leads the whole contribution process, working closely with the contributor where needed but generally leading execution.

The contributor owns execution with no involvement from the Design System team. This is the default level of support for contributions to the extended layer.