Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 2,931
-
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"
-
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"
-
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"
-
Customer Success (CS) Top 10 List for Product for 2018CQ2
-
Customer Success (CS) Top 10 List for Product for 2018CQ3
-
Issues related to cleaning up our CSS as part of the GitLab UI working group
-
Tasks part of the OKR aiming to reduce technical debt of our CSS
-
Issue for @courtmeddaugh to work on that is not a current priority.
-
Apply label to bug reports which are no longer reproducible in production. Notify requestor and close the issue.