Labels

Medium priority work for Growth Product team - important for roadmap but can be deferred if P1 work is available to pick up.

Lower priority work for Growth team - if this is an easy lift and/or you have time between P1 and P2 initiatives, this can be worked as lowest priority

PM help is needed for this issue

Issues where the PM review has been worked through and is ready to be scheduled

Do we want to implement this in our product?

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"

Used for MRs created as part of Pajamas Migration Day

Issues related to GitLab's internal use of Pendo for collection and analysis