Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Part of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
Part of the triage process for Create:Code Creation https://handbook.gitlab.com/handbook/engineering/development/dev/create/code-creation/milestone_planning/#planning-and-triage-process
-
Label used to track work related to improving data integrity across gitlab (as it pertains to project Compass). https://about.gitlab.com/direction/product-intelligence/#resolve-data-integrity-concerns
-
Issues that are related to competing with another tool or solution identified during Competitive Roadmap Reviews
-
An issue which has been validated, broken down, planned/designed, developed, deployed, but not verified in production. 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, deployed, and verified in production. 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
-
Issue with high technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
-
Issue with low technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
-
Issue with medium technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
-
Pajamas Design System: Broadcast message component
Prioritized