Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
this label is used by automated product operations release pages
-
Issues and merge request related to Engineering tooling such as pipeline or workflow
-
Label for issues relating to GitLab's customer purchasing experience, the customer portal and the billing & subscriptions model for GitLab EE.
-
The Technical Writing team is actively working on this item. (In Progress)
-
The Technical Writing team has completed its work on this item.
-
The Technical Writing effort for this has been identified, and no additional reminders are required from the bot.
-
Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
-
Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
-
Any issue/MR that contains work to support the implementation of a feature and/or results in an improvement in the user experience. Read more at https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
-
When using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.
-
Upkeeping efforts and catch-up corrective improvements that are not Feature nor Bugs. Read more at https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
-
denotes information regarding the user's journey through our tech stack
Prioritized