Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • advisoryerror
    GitLab.org / GitLab CVE assignments
    An error has occurred and is being investigated.
  • advisoryrejected
    GitLab.org / GitLab CVE assignments
    Advisory is rejected by MITRE and is being investigated.
  • advisorypublished
    GitLab.org / GitLab CVE assignments
    6/6: Advisory is published and available on MITRE.
  • advisorypublishing
    GitLab.org / GitLab CVE assignments
    5/6: Advisory is submitted to MITRE and awaiting status change.
  • advisoryassigned
    GitLab.org / GitLab CVE assignments
    4/6: Advisory is assigned a CVE ID and awaiting final approval.
  • advisoryassign-cve
    GitLab.org / GitLab CVE assignments
    3/6: Advisory is reviewed and awaiting CVE number assignment.
  • advisoryreviewing
    GitLab.org / GitLab CVE assignments
    2/6: Advisory is valid and awaiting review.
  • advisoryqueued
    GitLab.org / GitLab CVE assignments
    1/6: Advisory is new and awaiting validation.
  • advisory-scheduleimmediate
    GitLab.org / GitLab CVE assignments
    Advisory is ready to be published ASAP.
  • advisory-cve-idimmediate
    GitLab.org / GitLab CVE assignments
    Advisory needs CVE number assignment ASAP.
  • submissioninvalid
    GitLab.org / GitLab CVE assignments
    Submission has semantically invalid or missing data.
  • mitresubmitted
    GitLab.org / GitLab CVE assignments
    Advisory has been submitted to MITRE.
  • submissionvalid
    GitLab.org / GitLab CVE assignments
    Submission is semantically valid.
  • advisory-schedulewait
    GitLab.org / GitLab CVE assignments
    Advisory is not ready to be published.
  • advisory-groupgitlab
    GitLab.org / GitLab CVE assignments
    Advisory relates to GitLab.
  • advisory-groupexternal
    GitLab.org / GitLab CVE assignments
    Advisory relates to an external project hosted on GitLab.
  • advisorymitre-published
    GitLab.org / GitLab CVE assignments
    Deprecated: Advisory is published and available on MITRE.
  • advisorymitre-notified
    GitLab.org / GitLab CVE assignments
    Deprecated: Advisory is submitted to MITRE and awaiting status change.

    • Other labels

  • workhorse
    GitLab.org
    Issues on both the GitLab Workhorse and GitLab CE projects
  • workflowversion promoted
    GitLab.org
    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
  • workflowverification
    GitLab.org
    Everything has been merged, waiting for verification after a deploy.
  • workflowvalidation backlog
    GitLab.org
    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.
  • workflowstaging-canary
    GitLab.org
    Merge request is deployed to the staging canary environment.
  • workflowstaging
    GitLab.org
    Merge request has been deployed to staging.gitlab.com.
  • workflowsolution validation
    GitLab.org
    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
    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.
  • workflowready for development
    GitLab.org
  • workflowready for design
    GitLab.org
    (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
  • workflowproblem validation
    GitLab.org
    Workflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
  • workflowpost-deploy-db-staging
    GitLab.org
    Post-migrations on the merge request have been executed in staging.gitlab.com.
  • workflowpost-deploy-db-production
    GitLab.org
    Post-migrations on the merge request have been executed in GitLab.com
  • workflowplanning breakdown
    GitLab.org
    Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/
  • workflowneeds issue review
    GitLab.org
    Product managers use this label when their issue needs to be reviewed.