Labels
Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
-
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
-
customer+GitLab.orgFeatures and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 3,602
-
tw-leadmetaGitLab.orgMeta items relating to the TW Stage Leads processes. https://handbook.gitlab.com/handbook/product/ux/technical-writing/workflow/#stage-leads
-
tw-leadplanGitLab.orgItems that are driven by or require input from the Plan Technical Writing stage lead (Marcin).
-
tw-leadverifyGitLab.orgItems that are driven by or require input from the Verify Technical Writing stage lead https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads.
-
tw-styleGitLab.orgRelated to style standards for documentation, UI text (per Pajamas Content guide), or the Release Post.
-
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-weight1GitLab.org(optional) Technical Writing team member's effort, similar to fixing a single misspelling or adding a punctuation
-
tw-weight13GitLab.org(optional) Technical Writing team member's effort, similar to creating an entirely new page for a feature or process
-
tw-weight3GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a few sentences
-
tw-weight5GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a section of content
-
tw-weight8GitLab.org(optional) Technical Writing team member's effort, similar to revising a full page of provided content, or developing a half page
-
twtriagedGitLab.orgThe Technical Writing effort for this has been identified, and no additional reminders are required from the bot.
-
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://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
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
-
typemaintenanceGitLab.orgUpkeeping efforts and catch-up corrective improvements that are not Feature nor Bugs. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- 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/