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
-
workflowissue reviewedGitLab.orgProduct managers use this label when they've completed an issue peer review.
-
workflowneeds issue reviewGitLab.orgProduct managers use this label when their issue needs to be reviewed.
-
workflowplanning breakdownGitLab.orgIssues that need estimation, and possibly breaking down into further chunks to enable effective iteration https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowpost-deploy-db-productionGitLab.orgPost-migrations on the merge request have been executed in GitLab.com
-
workflowpost-deploy-db-stagingGitLab.orgPost-migrations on the merge request have been executed in staging.gitlab.com.
-
workflowproblem validationGitLab.orgWorkflow label for validating if the problem is customer relevant. https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-2-problem-validation
-
workflowready for designGitLab.org(optional) PM and Design prioritized design backlog of the next issues to be done https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-3-design
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowready for reviewGitLab.orgMerge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.
-
workflowrefinementGitLab.orgIssues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowschedulingGitLab.orgIssues that are ready for development but are not yet active (or have an associated release) https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-1-plan
-
workflowsolution validationGitLab.orgWorkflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-4-solution-validation