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,476
-
workflowcompleteGitLab.orgApplied after all MRs have merged and the issue has been verified if necessary https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-3-launch
-
workflowdesignGitLab.orgIdeate solutions to well-defined customer problems https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-3-design
-
workflowfailed current versionGitLab.orgWas not advanced beyond the current version (experimental or beta). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
-
workflowfeature-flaggedGitLab.orgEnabled through a separate feature flag rollout issue. https://handbook.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution/#workflow
-
workflowin devGitLab.orgIssues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowin reviewGitLab.orgIssues that are undergoing code review by the development team and/or undergoing design review by the UX team https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
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-flow/#description-4
-
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-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-flow/#outcomes-and-activities-2
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
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-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-flow/#description-4