Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
For issues that are actively being worked on in the current quarter
-
For issues that are inactive and not being worked on in the current quarter
-
used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized but not yet scheduled
-
used in conjunction with sales enablement sessions to indicate when a session topic has been prioritized and scheduled
-
plans, methods, or series of maneuvers or stratagems for obtaining specific goals or results
-
To signify a Support Ops issue/MR is a change level 1
-
To signify a Support Ops issue/MR is a change level 2
-
To signify a Support Ops issue/MR is a change level 3
-
To signify a Support Ops issue/MR is a change level 4
-
Issues related to team management, team infrastructure and general team tasks
-
Customer Support department. https://handbook.gitlab.com/handbook/support/
-
Environment Automation Team label used to identify issues, MRs, epics owned by the Environment Automation Team in GitLab Dedicated Group
-
For work being performed by the Product Security Engineering Team: https://handbook.gitlab.com/handbook/security/security-engineering/product-security-engineering/
-
Scalability:Projections team https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability
Prioritized