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

  • CISA Known Exploited Vulnerability
    GitLab.org
    Vulnerabilities in CISA's KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • 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
  • CPO Interest
    GitLab.org
  • 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
  • CSOps
    GitLab.org
  • 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.
  • CVMIn Progress
    GitLab.org
    Currently being worked on by @courtmeddaugh.