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/product-development/how-we-work/issue-triage/#priority
-
severity1GitLab.orgBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/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/product-development/how-we-work/issue-triage/#priority
-
severity2GitLab.orgCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
priority3GitLab.orgWe want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority
-
severity3GitLab.orgMajor - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
priority4GitLab.orgWe don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority
-
severity4GitLab.orgLow - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
MaintenanceGitLab.org / omnibus-gitlabChange requests, eg. version upgrade of software, default configuration value change.
Labels 4,145
-
teamFrameworksGitLab.orgScalability:Frameworks team https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability
-
teamsGitLab.orgIssues and Epics relating to teams, which is a feature owned by the Manage:Spaces group
-
technical debtGitLab.orgWork items to clean up or improve existing code that needs attention. This includes follow-ups from code reviews and areas we've identified that could have better implementations. See gitlab-com/content-sites/handbook!10641.
-
test-health:pass-after-retryGitLab.orgA test that first failed, and then passed when retried in the same CI/CD job.