Prioritized Labels

  • priority1
    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
    GitLab.org
  • severity1
    Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
    GitLab.org
  • priority2
    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
    GitLab.org
  • severity2
    Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
    GitLab.org
  • priority3
    We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    GitLab.org
  • severity3
    Major - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
    GitLab.org
  • priority4
    We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    GitLab.org
  • severity4
    Low - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
    GitLab.org
  • Maintenance
    Change requests, eg. version upgrade of software, default configuration value change.
    GitLab.org / omnibus-gitlab
  • Internal
    Any work that is not customer/user facing.
    GitLab.org / omnibus-gitlab
  • Other Labels

  • 🍎
    🍎 Used by the Fulfillment group to identify potentially quick wins that have a weight of 2 or less - i.e. low hanging fruit
    GitLab.org
  • 🏓
    Awaiting community member action or response. This label is used by the Contributor Success team.
    GitLab.org
  • 👩‍💻 CodeChallenge.dev
    MRs that originated from a CodeChallenge.dev user
    GitLab.org
  • #field-fyi
    Earmarked to notify the sales team of issue updates.
    GitLab.org
  • 1st contribution
    First contribution from a community member
    GitLab.org
  • 2021-db-training
    Issues that you want to look with the trainer and other trainees in the working sessions of 2021 PostgreSQL database training
    GitLab.org
  • 2021Q1 gitlab.com Latency Degradation
    GitLab.org
  • 2FA
  • API Limits
    GitLab.org
  • APM
    Issues for Application Performance Monitoring (APM), part of the Monitor stage of the DevOps lifecycle
    GitLab.org
  • AR-0open
    Access Request opened and has not been seen, worked on, or added to backlog
    GitLab.org
  • AR-1needs manager approval
    Access Request pending Manager Approval
    GitLab.org
  • AR-2backlog
    Access Requests with assigned, approval labels, and ready to go
    GitLab.org
  • AR-3in progress
    Access Request currently in progress
    GitLab.org
  • AR-4on hold
    Access Request pending licenses
    GitLab.org
  • ARM
    GitLab.org
  • ASC
    Issues that are designated to be tackled as part of the Advanced Software Course
    GitLab.org
  • AST Leadership
    Issues and epics related to the Secure & Defend Section FY21 initiative to be recognized as a AST leader by accelerating maturity of SAST, DAST, Dependency Scanning, Fuzz Testing, and Vulnerability Management.
    GitLab.org
  • Abuse Prevention
    To be used for all abuse prevention related features and proposals for GitLab.com, EE and CE
    GitLab.org
  • Accepting merge requests
    Issues opened for contribution from the Community. Issue's weight is an estimation of complexity. Please mention @gitlab-org/coaches if you have any questions :)
    GitLab.org