Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
usecase-CloudNativeGitLab.com / marketingCustomer use case - Cloud Native - https://about.gitlab.com/handbook/use-cases/
-
usecase-CIGitLab.com / marketingCustomer use case - Continuous Integration - https://about.gitlab.com/handbook/use-cases/
-
usecase-CDGitLab.com / marketingCustomer use case - Continuous Deliver - https://about.gitlab.com/handbook/use-cases/
-
usecase-AgileGitLab.com / marketingCustomer use case - Agile Project Mgt - https://about.gitlab.com/handbook/use-cases/
-
typemaintenanceGitLab.comUpkeeping 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
-
typeignoreGitLab.comWhen using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.
-
typefeatureGitLab.comAny 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
-
typedirectionGitLab.comIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
-
typebugGitLab.comIssues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
-
twtriagedGitLab.comThe Technical Writing effort for this has been identified, and no additional reminders are required from the bot.
-
transactionsGitLab.comLabel for issues relating to GitLab's customer purchasing experience, the customer portal and the billing & subscriptions model for GitLab EE.
-
toolingGitLab.comIssues and merge request related to Engineering tooling such as pipeline or workflow
Prioritized