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

  • CI/CD UX Team
    GitLab.org
    Used by the UX CI/CD Team to track process and activities (DRI: Product Design Manager) https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/ci-cd/
  • CISP1
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP2
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP3
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP4
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CM scorecard
    GitLab.org
    Issues related to the Category Maturity Scorecards process
  • CRM
    GitLab.org
    Customer Relationship Management
  • CS Top 10 (2018CQ2)
    GitLab.org
    Customer Success (CS) Top 10 List for Product for 2018CQ2
  • CS Top 10 (2018CQ3)
    GitLab.org
    Customer Success (CS) Top 10 List for Product for 2018CQ3
  • CSAT-Priority1
    GitLab.org
    customer satisfaction priority
  • CSAT-Priority2
    GitLab.org
    customer satisfaction priority
  • CSAT-Priority3
    GitLab.org
    customer satisfaction priority
  • CSS Component
    GitLab.org
    Adding or changing a CSS component
  • CSS cleanup
    GitLab.org
    Issues related to cleaning up our CSS as part of the GitLab UI working group
  • CSS optimization
    GitLab.org
    Tasks part of the OKR aiming to reduce technical debt of our CSS
  • CVMBacklog
    GitLab.org
    Issue for @courtmeddaugh to work on that is not a current priority.
  • CVMDone
    GitLab.org
    Issue @courtmeddaugh has finished working on.