Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Issues Alex Martin is considering for group::utilization in 17.1
-
Issues Alex is consider for group::utilization in 17.0
-
Issues belonging to the Secret Detection group of the Secure stage. See https://handbook.gitlab.com/handbook/product/categories/#secret-detection-group
-
Moved from `group::provision` to `group::fulfillment platform`.
-
Related to the Self-Managed provisioning method of legacy licensing. Owned by `group::provision`.
-
Category for the provisioning of base plan subscriptions, owned by `group::provision`.
-
Category for the provisioning of add-on products, owned by `group::provision`.
-
Issues Alex Martin is consider for 16.11 milestone for group::utilization
-
Maintenance issues for group::purchase in the Billable Members category
-
Issues belonging to the Authorization group of the Govern stage of the DevOps lifecycle, https://about.gitlab.com/handbook/product/categories/#authorization-group
-
Issues belonging to the Authentication group of the Govern stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#authentication-group
-
Issues Alex Martin is consider prioritizing for 16.6 Milestone for group::utilization
-
GitLab.org label for Digital Experience Team https://about.gitlab.com/handbook/marketing/digital-experience/
-
Duo Chat group, part of the AI-powered stage within the Data Science section
-
Code Creation group. Part of the Create stage. Works on Code Suggestions.
-
Editor Extension group for all IDE plugins. Part of the Create stage.
-
For issues related to large migrations performed by our importers. This should only be used by group::import and integrate
Prioritized