Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • priority1
    GitLab.com
    We will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority2
    GitLab.com
    priority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority3
    GitLab.com
    We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority4
    GitLab.com
    We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • cto-cos-meta
    GitLab.com / Chief of Staff to the CTO
  • CoS-to-CTO
    GitLab.com
    Issues and MRs related to or of interest to the Chief of Staff to CTO
  • repeat task
    GitLab.com / Chief of Staff to the CTO
    Items that should be done by each CoS to the CTO
  • retrospective
    GitLab.com / Chief of Staff to the CTO
  • Other labels

  • okrAt Risk
    GitLab.com
    OKR is at risk
  • okrCompleted
    GitLab.com
    OKR that has been completed.
  • okrDelayed
    GitLab.com
    OKR is behind schedule
  • okrOn Track
    GitLab.com
    OKR is on-track
  • onboarding
    GitLab.com
    created by BT for the group (other label is only project level and doesn't inherit)
  • optimizer
    GitLab.com
    Issues related to salesforce optimizer results
  • outage
    GitLab.com
    A production incident that has any customer impact
  • pbp-DIB
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a Diversity, Inclusion, & Belonging issue
  • pbp-LD
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a Learning & Development issue
  • pbp-TR
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a Total Rewards issue
  • pbp-attention
    GitLab.com
    This label should be added by any team member who requires People Business Partner attention/review/feedback on an issue
  • pbp-done
    GitLab.com
    This label should be added by a member of the People Business Partner team to indicate that the issue has been reviewed
  • pbp-legal
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a Legal issue
  • pbp-other
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration with another team (outside of Total Rewards, L&D, DIB, Recruiting, People Ops, or Legal)
  • pbp-peopleops
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a People Ops issue
  • pbp-recruiting
    GitLab.com
    This label should be added by a People Business Partner to indicate collaboration on a Recruiting issue
  • pbphigh
    GitLab.com
    This label should be added by a People Business Partner during triaging to indicate "urgent" priority
  • pbplow
    GitLab.com
    This label should be added by a People Business Partner during triaging to indicate "low" priority