Merge request is deployed to the canary environment.

Applied after all MRs have merged and the issue has been verified if necessary

Ideate solutions to well-defined customer problems https://about.gitlab.com/handbook/product-development-flow/#validation-phase-3-design

Was not advanced beyond the current version (experimental or beta). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html

Issues for features that are being enabled through a separate feature flag rollout issue

Issues that are actively being worked on by a developer

Issues that are undergoing code review by the development team and/or undergoing design review by the UX team

Product managers use this label when they've completed an issue peer review.

Product managers use this label when their issue needs to be reviewed.

Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/

Post-migrations on the merge request have been executed in GitLab.com

Post-migrations on the merge request have been executed in staging.gitlab.com.

Workflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary

Merge request has been deployed to GitLab.com

(optional) PM and Design prioritized design backlog of the next issues to be done

Merge 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.

Issues that need further input from team members in order for it to be "workflow::ready for development"

Issues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/

Workflow label for validating that the proposed solution meets user needs. https://about.gitlab.com/handbook/product-development-flow/