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

  • sko-statusWIP
    GitLab.com
    Work in progress that has been accepted and assigned to a DRI
  • sko-statusplan
    GitLab.com
    Work that is proposed, in an exploratory state
  • sprint-additions
    GitLab.com
    This issue was not originally in the sprint and was added after the sprint started.
  • statusactive
    GitLab.com
    For issues that are actively being worked on in the current quarter
  • statusinactive
    GitLab.com
    For issues that are inactive and not being worked on in the current quarter
  • statusplan
    GitLab.com
    used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized but not yet scheduled
  • statusscheduled
    GitLab.com
    used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized and scheduled
  • strategy
    GitLab.com
    plans, methods, or series of maneuvers or stratagems for obtaining specific goals or results
  • support-ops-change1
    GitLab.com
    To signify a Support Ops issue/MR is a change level 1
  • support-ops-change2
    GitLab.com
    To signify a Support Ops issue/MR is a change level 2
  • support-ops-change3
    GitLab.com
    To signify a Support Ops issue/MR is a change level 3
  • support-ops-change4
    GitLab.com
    To signify a Support Ops issue/MR is a change level 4
  • supportdone
    GitLab.com
    Access Request provisioning completed
  • supportto do
    GitLab.com
    Access Request pending provisioning from Support
  • team-tasks
    GitLab.com
    Issues related to team management, team infrastructure and general team tasks