Skip to content
Snippets Groups Projects

Prioritized labels 10

Drag to reorder prioritized labels and change their relative priority.
  • priority1
    GitLab.org
    We will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
  • severity1
    GitLab.org
    Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
  • priority2
    GitLab.org
    We will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
  • severity2
    GitLab.org
    Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
  • severity3
    GitLab.org
    Major - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
  • severity4
    GitLab.org
    Low - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
  • Maintenance
    GitLab.org / omnibus-gitlab
    Change requests, eg. version upgrade of software, default configuration value change.
  • Internal
    GitLab.org / omnibus-gitlab
    Any work that is not customer/user facing.
  • Labels 3,146

  • Product managers use this label when they've completed an issue peer review.
  • Product managers use this label when their issue needs to be reviewed.
  • workflownext
    GitLab.org
    Issues that are ready for development and should be worked on next.
  • Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration https://handbook.gitlab.com/handbook/product-development-flow/#description-4
  • Post-migrations on the merge request have been executed in GitLab.com
  • Post-migrations on the merge request have been executed in staging.gitlab.com.
  • workflowproduction
    GitLab.org
    Merge request has been deployed to GitLab.com
  • (optional) PM and Design prioritized design backlog of the next issues to be done https://handbook.gitlab.com/handbook/product-development-flow/#outcomes-and-activities-2
  • Merge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.
  • workflowrefinement
    GitLab.org
    Issues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-1-plan
  • workflowscheduling
    GitLab.org
    Issues that are ready for development but are not yet active (or have an associated release) https://handbook.gitlab.com/handbook/product-development-flow/#description-4
  • workflowstaging
    GitLab.org
    Merge request has been deployed to staging.gitlab.com.
  • Merge request is deployed to the staging canary environment.
  • workflowstaging-ref
    GitLab.org
    Merge request is deployed to the staging ref environment.
  • workflowstart
    GitLab.org
    The entry point for workflow scoped labels. From here, Issues will either move through the validation workflow, go directly to planning and scheduling, or in certain cases, go directly to the development steps.
  • Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://handbook.gitlab.com/handbook/product-development-flow/#workflow-summary
  • Everything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development-flow/#description-5