Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • Category:Serverless
    GitLab.org
    All issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
  • dockerfile
    GitLab.org / GitLab Docs
    Related to the dockerfiles present in the gitlab-docs project
  • Issues related to chaos engineering (part of ~devops:configure stage)
  • docs-discussion
    GitLab.org / GitLab Docs
    Ongoing discussions for the docs team
  • [DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
  • kramdown
    GitLab.org / GitLab Docs
    Kramdown related issues
  • All issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
  • [deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
  • Issues belonging to the Monitor stage Health group for product category Cluster Monitoring
  • Issues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
  • All issues and MRs related to the code quality category within devops:verify https://about.gitlab.com/direction/verify/code_quality
  • Category label - Features that apply to management container registries
  • [DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
  • All issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
  • Please select Runner Core, Runner SaaS, or Runner Fleet
  • Issues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
  • operations
    GitLab.org
    Issues for Operations, part of the Configure stage of the DevOps lifecycle
  • Issues related to the "cluster cost optimization" category of the configure stage. See &503
  • Charts
    GitLab.org
    Related to the Charts components built on gitlab-ui
  • Changes or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
  • groupsource code
    GitLab.org
    Issues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
  • grouprunner
    GitLab.org
    Issues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
  • Relating the `Kubernetes Management` category within the configure stage
  • rails6
    GitLab.org
    Issues and Merge Requests related to upgrading to Rails 6
  • 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
  • workflowtw-test-status
    GitLab.org / GitLab Docs
    Testing per #771
  • 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"
  • 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/