Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • (perceived) data loss
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    An event that is seen as data loss from an external user
  • IncidentReview
    GitLab.com / GitLab Infrastructure Team
  • critical
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Things that really, really, really matter
  • 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
  • severity1
    GitLab.com
    Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
  • severity2
    GitLab.com
    Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
  • 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
  • unblocks others
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Help other people
  • goal
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Something we committed to do in the WoW
  • Other labels

  • Application added to the tech stack but information is incomplete
  • Tasks to be completed by teams other than EntApps
  • BT-TechStackTo do
    GitLab.com
    New issue, not worked on yet
  • BTApproved
    GitLab.com
    Approved Changes to system.
  • BTBacklog
    GitLab.com
    Business Technology team tasks to be prioritized or nice to haves, but not critical
  • BTBlocked
    GitLab.com
    Changes to system pending approval.
  • BTDone
    GitLab.com
    Business Technology team tasks completed.
  • BTDone External
    GitLab.com
    Business Technology team tasks completed on a non BT Project Issue
  • BTIn Progress
    GitLab.com
    Business Technology tasks being worked on.
  • Problem statement and expected outcome not defined by requester. Not ready to be worked on.
  • BTReady for Review
    GitLab.com
    MR is ready for review
  • BTReady to Build
    GitLab.com
    Clear definition and approval, now ready to be worked on. Next Phase is BT::In Progress
  • BTReady to Deploy
    GitLab.com
    Change is ready for deployment
  • BTTo Do
    GitLab.com
    Business Technology tasks planned.
  • Backblaze
    GitLab.com
    general label used for issues or MRs related to Backblaze
  • Issues related to Sidekiq and background job processing
  • Use this label when the automatically Suggested Reviewer is not useful (Feature of AI-powered stage)