Labels

(Very large) Complicated changes introducing a new user flow that connects with other large flows and may require input from other designers, product managers, or engineers from the same or another stage group. This is the largest flow design/redesign that we would take on in a single milestone. This requires research where the designer may or may not be working with a researcher to plan and conduct exploratory interviews or user testing sessions

[Monitor] Design Issues that have been planned but not started

[Monitor] Design Issues that are in the Discovery phase (Fact finding, research, user journeys, story maps)

[Monitor] Design Issues that are in progress (wireframes, mockups, prototypes, etc...)

[Monitor] Design Issues that are ready for engineering (can be closed issues, linked to engineering issues)

[Monitor] Design Issues that are ready for review (Design review && Engineering review)

Denotes collaboration between Development and Quality

Changes or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)

Support requests for the Development Analytics team, covering issues, enhancements, or questions related to tools, processes, and workflows within the Development Analytics scope.

Issues related to technical debt identified or managed by the development-analytics team - including code refactoring, architecture improvements, dependency updates, and system optimization tasks.

Any work item related to pipeline stability

Support requests for the Development Tooling team, covering issues, enhancements, or questions related to tools, processes, and workflows within the Development Tooling scope.

A security issue which has been validated, broken down, planned/designed, developed and is waiting for a security release to be deployed. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down, planned/designed, but development is blocked until another issue is complete. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down, planned/designed, developed and is in review. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down/planned/designed and is ready for development to begin. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down/planned/designed and is in development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382