Labels

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"

Issues related to the Category Maturity Scorecards process

Code purpose efforts

CP AunthN/Z Foundation label for Phase 0 - Detailed Design

Code Purple AuthN/Z GATE Phase 1 - Realm control plane established with global Spanner database integrated into our cellular architecture

Code Purple AuthN/Z GATE Phase 2 - Global authentication and authorization data synchronization from deployment units to real-wide database

Code Purple AuthN/Z GATE Phase 3 - GitLab Adaptive Trust Environment "GATE" in production, reducing software supply chain risks by introduction isolation from our monolithic codebase

Code Purple AuthN/Z GATE Phase 4 - Regional GitLab Adaptive Trust Environment "GATE" functional, providing fine-grained access controls available for consumption by developers

Code Purple AuthN/Z GATE Phase Other - doesn't fit one of the defined phases 0 - 4

Customer Relationship Management

Customer Success (CS) Top 10 List for Product for 2018CQ2

Customer Success (CS) Top 10 List for Product for 2018CQ3

customer satisfaction priority

customer satisfaction priority

customer satisfaction priority

Adding or changing a CSS component

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.