Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • Pick into 3.3.x
    GitLab.org / charts / GitLab Chart
  • Pick into 4.0.x
    GitLab.org / charts / GitLab Chart
    Pick into 4-0-stable branch
  • Pick into 4.1.x
    GitLab.org / charts / GitLab Chart
    Pick into 4-1-stable branch
  • Pick into 3.2.x
    GitLab.org / charts / GitLab Chart
  • Maintenance
    GitLab.org / charts / GitLab Chart
    Regular maintenance work, eg. version and configuration changes
  • Research
    GitLab.org / charts / GitLab Chart
  • Other labels

  • Engineering Time
    GitLab.org
    Indicates the issue was prioritized by Engineering. Used for metrics related to Product/Engineering prioritization split.
  • Features or changes limited or intended as part of GitLab Duo Enterprise.
  • GitLab Duo Pro
    GitLab.org
    Features or changes limited or intended as part of GitLab Duo Pro.
  • Master broken incidents caused by db:migrate:multi-version-upgrade job, see example: gitlab-org/quality/engineering-productivity/master-broken-incidents#5982
  • Track Security Requirements on different projects
  • This label is used by the Application Security team to apply when the IC on rotation gets pinged during their triage rotation
  • Label to prevent duplicate notes from the triage-ops bot for customer bugs without a severity
  • AppSec work not covered by other AppSecWorkType labels
  • AppSec work associated with stable counterpart duties
  • AppSec Threat Modeling work
  • AppSecWorkTypeKR
    GitLab.org
    Work associated with AppSec OKRs and KRs
  • ee ui/ux needed
    GitLab.org
    Issues requiring assistance from UI/UX for Editor Extensions.