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/product-development/how-we-work/issue-triage/#priority
-
severity1GitLab.orgBlocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/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/product-development/how-we-work/issue-triage/#priority
-
severity2GitLab.orgCritical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
priority3GitLab.orgWe want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority
-
severity3GitLab.orgMajor - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
priority4GitLab.orgWe don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#priority
-
severity4GitLab.orgLow - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/#severity
-
MaintenanceGitLab.org / omnibus-gitlabChange requests, eg. version upgrade of software, default configuration value change.
Labels 4,145
-
trackbuildGitLab.orgItems that belong to the build track only | https://about.gitlab.com/handbook/product-development-flow/
-
trackvalidationGitLab.orgItems that belong to the validation track only | https://about.gitlab.com/handbook/product-development-flow/
-
tracking operational readinessGitLab.orgIssue or Work Item is being tracked for Operational Readiness
-
triage policyGitLab.orgDescribing introductions of or changes to issue triage policies in this project
-
triage questionGitLab.orgIssues which have a question that needs to be answered before they can be triaged (added to a milestone)
-
ttisupport-requestGitLab.org(obsolete) Request for support by the Test & Tools Infrastructure team
-
tw-leadai-poweredGitLab.orgItems that are driven by or require input from the AI-powered Technical Writing stage lead https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads.
-
tw-leadapplication security testingGitLab.orgItems that are driven by or require input from the Application Security Testing Technical Writing stage lead https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads.
-
tw-leadcreateGitLab.orgItems that are driven by or require input from the Create Technical Writing stage lead https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads.
-
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.