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,833
-
won't doGitLab.orgThis request is being closed as our current focus isn't in this area. While this feature may have merit, we need to prioritize our efforts elsewhere at this time. If you'd like to provide additional context about why this feature is important, please comment on this issue as this will help us better evaluate the feature if we revisit this area in the future.
-
work itemsdogfooding-epicsGitLab.orgItems related to epics migration that should be completed prior to internal rollout.
-
work itemsdogfooding-issuesGitLab.orgItems related to migrating issues to work items that should be completed prior to any internal rollout.
-
work itemsga-epic_SMGitLab.orgMust be addressed prior to rolling the new experience out to self-managed users.
-
work itemsissues-ga_immediate-followGitLab.orgThese are items which are not GA-issues blockers but must be addressed as P1 post GA-issues.
-
work itemspost-ga-firstGitLab.orgFirst priority after both issues and epic work items are GA. Does not block any rollout.
-
work itemspost-ga-laterGitLab.orgNon-blocking work items updates that are not top priority after migration.