Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • security
    GitLab.org
    Issues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
  • customer
    GitLab.org
    Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
  • customer+
    GitLab.org
    Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
  • regression
    GitLab.org
    Issues with this label are regressions from the previous non-patch release
  • typebug
    GitLab.org
    Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
  • direction
    GitLab.org
    Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
  • high priority
    GitLab.org / gitlab-runner
    Other important issues
  • Other labels

  • workhorse
    GitLab.org
    Issues on both the GitLab Workhorse and GitLab CE projects
  • Successfully completed the current version (experimental or beta) and promoted to the next version (beta or GA). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
  • Everything has been merged, waiting for verification after a deploy.
  • Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
  • 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.
  • workflowstaging-ref
    GitLab.org
    Merge request is deployed to the staging ref environment.
  • Merge request is deployed to the staging canary environment.
  • workflowstaging
    GitLab.org
    Merge request has been deployed to staging.gitlab.com.
  • Workflow label for validating that the proposed solution meets user needs. https://about.gitlab.com/handbook/product-development-flow/
  • workflowscheduling
    GitLab.org
    Issues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/
  • workflowrefinement
    GitLab.org
    Issues that need further input from team members in order for it to be "workflow::ready for development"
  • workflowready-for-review
    GitLab.org / gitlab-runner
  • 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.
  • (optional) PM and Design prioritized design backlog of the next issues to be done
  • workflowproduction
    GitLab.org
    Merge request has been deployed to GitLab.com
  • Workflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
  • Post-migrations on the merge request have been executed in staging.gitlab.com.
  • Post-migrations on the merge request have been executed in GitLab.com
  • Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/