Labels
Prioritized labels 5
Drag to reorder prioritized labels and change their relative priority.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
maintenancerefactorGitLab.orgIssues related to things that need improvement and that have been left behind due to high velocity of development
Labels 3,521
-
CI/CD UX TeamGitLab.orgUsed 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/
-
CISA Known Exploited VulnerabilityGitLab.orgVulnerabilities in CISA's KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
-
CISP1GitLab.orgPriority 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"
-
CISP2GitLab.orgPriority 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"
-
CISP3GitLab.orgPriority 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"
-
CISP4GitLab.orgPriority 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"
-
CP Phase1 - RCP + SpannerGitLab.orgCode Purple AuthN/Z GATE Phase 1 - Realm control plane established with global Spanner database integrated into our cellular architecture
-
CP Phase2 - GDS AuthNZGitLab.orgCode Purple AuthN/Z GATE Phase 2 - Global authentication and authorization data synchronization from deployment units to real-wide database
-
CP Phase3 - GATE ProdGitLab.orgCode 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
-
CP Phase4.- Regional GATEGitLab.orgCode Purple AuthN/Z GATE Phase 4 - Regional GitLab Adaptive Trust Environment "GATE" functional, providing fine-grained access controls available for consumption by developers
-
CP PhaseOtherGitLab.orgCode Purple AuthN/Z GATE Phase Other - doesn't fit one of the defined phases 0 - 4