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

  • BT Finance Systems
    GitLab.com
    For anything related to a Finance System (i.e. Zuora, Netsuite, Tipalti, Expensify, etc.). Catch all to ensure a Finance Systems Admin is aware and can triage as necessary.
  • High level BT Integrations tag for roadmap issues and epics. Not to be used for granular work, see BT Integrations::Backlog and BT Integrations::Kanban instead
  • Business Technology Integrations Backlog
  • Add to the Kanban board
  • BT PS Hold
    GitLab.com
    Items not ready or on hold/delayed.
  • BT Roadmap
    GitLab.com
    BT Roadmap
  • This stage is essentially a backlog of proposals which are subject to review.
  • Business Technology Scoping
  • BT Stage 2-Planning
    GitLab.com
    Business Technology Formal Project Plan and Stakeholder Sign Off
  • BT Stage 3-Action
    GitLab.com
    Business Technology Implementation Projects
  • BT Stage 4-Strike
    GitLab.com
    Business Technology End of Project Activities
  • BT-FYI
    GitLab.com
    No direct action needed from Business Technology but awareness for potential questions