Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 4,179
-
The entry point for workflow scoped labels. From here, Issues will either move through the validation workflow, go directly to planning and scheduling, or in certain cases, go directly to the development steps.
-
Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#validation-phase-1-validation-backlog
-
Everything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/#build-phase-2-develop--test
-
Successfully completed the current version (experimental or beta) and promoted to the next version (beta or GA). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
-
Issues on both the GitLab Workhorse and GitLab CE projects
-
A work plan has been written to the Work Plan widget.
-
Remote Development Workspaces issues which have already been closed in previous iterations
-
Work related to "Big Rocks" across the organization.
-
Work to reduce friction and increase velocity. KTLO/BAU reduction.
-
Work to support teams or the product in ways that are either not yet automated or so infrequent they are not worth automation yet.
-
Label tracking work needed for Project Zero Console (gitlab-com/gl-infra&1426)
-
Designate issues that are required for GitLab Zoekt powered exact code search GA release