Labels
Prioritized labels 10
Drag to reorder prioritized labels and change their relative priority.
-
priority1GitLab.orgWe will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity1GitLab.orgBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority2GitLab.orgWe will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity2GitLab.orgCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority3GitLab.orgWe want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity3GitLab.orgMajor - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
priority4GitLab.orgWe don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
-
severity4GitLab.orgLow - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
-
MaintenanceGitLab.org / omnibus-gitlabChange requests, eg. version upgrade of software, default configuration value change.
Labels 3,670
-
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.
-
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
-
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