Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • Pick into 3.3.x
    GitLab.org / charts / GitLab Chart
  • Pick into 4.0.x
    GitLab.org / charts / GitLab Chart
    Pick into 4-0-stable branch
  • Pick into 4.1.x
    GitLab.org / charts / GitLab Chart
    Pick into 4-1-stable branch
  • Pick into 3.2.x
    GitLab.org / charts / GitLab Chart
  • Maintenance
    GitLab.org / charts / GitLab Chart
    Regular maintenance work, eg. version and configuration changes
  • Research
    GitLab.org / charts / GitLab Chart
  • Other labels

  • Feature in Category:CI
  • 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.