Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 144
-
Use this label when you want to mark the priority of a design issue as the top priority (i.e. do this first as the top priority 1) where you're expecting to deliver it at a 100% by the defined due date.
-
Use this label when you want to mark the priority of a design issue as the second most important priority (i.e. do this second as the next priority 2) where you're expecting to deliver it at 80% by the defined due date.
-
Use this label when you want to mark the priority of a design issue as the third-highest priority (i.e. do this third as the medium priority 3) where you're expecting to deliver it at 60% by the defined due date.
-
Use this label when you want to mark the priority of a design issue as the fourth-highest priority (i.e. do this later as a lower priority 4) where you're expecting to deliver it at 40% by the defined due date.
-
Use this label when you want to mark the priority of a design issue as the fifth-highest priority (i.e. do this later as a lower priority 5) where you're expecting to deliver it at 20% by the defined due date.
-
Use this label when you want to mark the priority of a design issue as the sixth-highest priority (i.e. do this last as the least priority 6) where you're expecting to deliver it at 10% by the defined due date.
-
A label to denote the priority for issues of the duo workflow group: https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/duo-workflow/.
-
A label to denote the priority for issues of the duo workflow group: https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/duo-workflow/.
-
A label to denote the priority for issues of the duo workflow group: https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/duo-workflow/.
-
Feb-Apr of 2025. When used with Interlock Priority label, do not change once approved.
-
May-July of 2025. When used with Interlock Priority label, do not change once approved.
-
Aug-Oct of 2025. When used with Interlock Priority label, do not change once approved.
-
Oct 2025 to Jan 2026. When used with Interlock Priority label, do not change once approved.
-
To identify Fulfillment section priority issues planned for Q4 of FY22
-
To identify critical issues related to improving the purchasing and provisioning experience for internal and external customers.
-
DEPRECATED. Use label `gitlab.com` instead, combined with P/S labels to indicate priority.