Labels
Prioritized labels 10
Drag to reorder prioritized labels and change their relative priority.
-
priority1GitLab.orgWe will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity1GitLab.orgBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority2GitLab.orgWe will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity2GitLab.orgCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority3GitLab.orgWe want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity3GitLab.orgMajor - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority4GitLab.orgWe don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity4GitLab.orgLow - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
MaintenanceGitLab.org / omnibus-gitlabChange requests, eg. version upgrade of software, default configuration value change.
Labels 3,481
-
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