Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 2,895
-
upstream depsGitLab.orgThis label represent issues that requires fixes too be developed upstream in dependency projects
-
upcoming security releaseGitLab.orgGitLab security releases. This label should only be added for (critical) security root/meta issues. Do not add this label to individual security issues and/or merge requests.
-
unplanned-upgrade-stopGitLab.orgThe label is for upgrade bugs which resulted in retroactively adding required upgrade stop to the Upgrade Path. Also applied to the relevant Root Cause Analysis issues for such upgrade bugs. https://handbook.gitlab.com/handbook/engineering/unplanned-upgrade-stop/
-
typemaintenanceGitLab.orgUpkeeping 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
- Lock on merge
- Issues
- Merge requests
- Epics
-
typeignoreGitLab.orgWhen using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.
- Lock on merge
- Issues
- Merge requests
- Epics
-
typefeatureGitLab.orgAny 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
- Lock on merge
- Issues
- Merge requests
- Epics
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
- Epics
-
twtriagedGitLab.orgThe Technical Writing effort for this has been identified, and no additional reminders are required from the bot.
-
tw-weight8GitLab.org(optional) Technical Writing team member's effort, similar to revising a full page of provided content, or developing a half page
-
tw-weight5GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a section of content
-
tw-weight3GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a few sentences
-
tw-weight13GitLab.org(optional) Technical Writing team member's effort, similar to creating an entirely new page for a feature or process
-
tw-weight1GitLab.org(optional) Technical Writing team member's effort, similar to fixing a single misspelling or adding a punctuation
-
tw-testingGitLab.orgRelated to tools, process, standards for doc/UI/Release Post content testing, including linting. Also use more-specific labels like ~vale or ~markdownlint, if applicable. Typically involving the Technical Writing Test Automation Committee.
-
tw-styleGitLab.orgRelated to style standards for documentation, UI text (per Pajamas Content guide), or the Release Post. Typically involving the Technical Writing Style Committee.