Labels
Prioritized labels 11
Drag to reorder prioritized labels and change their relative priority.
-
(perceived) data lossGitLab.com / GitLab Infrastructure Team / Production EngineeringAn event that is seen as data loss from an external user
-
priority1GitLab.comWe will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
severity1GitLab.comBlocker - 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
-
severity2GitLab.comCritical - 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.compriority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority3GitLab.comWe want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority4GitLab.comWe don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
unblocks othersGitLab.com / GitLab Infrastructure TeamWork that helps unblock other teams, often coming in as a request
Labels 4,129
-
secrisk-workflowblockedGitLab.comIssues that are blocked and need a resolution plan or escalation. Move to ~"secrisk-workflow::in progress" or ~"secrisk-workflow::ready" once unblocked.
-
secrisk-workflowcancelledGitLab.comIssue closed because the work was cancelled because it was no longer needed or relevant.
-
secrisk-workflowin progressGitLab.comIssues that are being actively worked by the team and should have a health status and an assignee. Stale issues with this label should be moved to blocked or cancelled.
-
secrisk-workflowproposalGitLab.comAn idea or opinion on how to proceed. It's been triaged/scoped but not yet considered "ready".
-
secrisk-workflowreadyGitLab.comIssue is well-defined, ready to be picked up, and assigned to the correct epic. No assignee. These issues will be picked up as other issues are closed. (To Do)
-
secrisk-workflowstalledGitLab.comThe issue has been deprioritized or is stale, but otherwise is not blocked by any other dependency. Consider moving moving to ~"secrisk-workflow::cancelled" (closes issue) or back to ~"secrisk-workflow::ready".
-
secrisk-workflowtriageGitLab.comSkip to ::ready if work is well defined. These issues need peer review or further refinement and prioritization so they can be included in the Ready bucket. (Should Do)