Related to style standards for documentation, UI text (per Pajamas Content guide), or the Release Post. Typically involving the Technical Writing Style Committee.

Related 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.

(optional) Technical Writing team member's effort, similar to fixing a single misspelling or adding a punctuation

(optional) Technical Writing team member's effort, similar to creating an entirely new page for a feature or process

(optional) Technical Writing team member's effort, similar to developing or revising a few sentences

(optional) Technical Writing team member's effort, similar to developing or revising a section of content

(optional) Technical Writing team member's effort, similar to revising a full page of provided content, or developing a half page

The Technical Writing team is actively working on this item. (In Progress)

The Technical Writing team has completed their work on this item.

The Technical Writing effort for this has been identified, and no additional reminders are required from the bot.

Any 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

When using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.

Upkeeping 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

Issues related to unit testing of GitLab code

The 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/

GitLab 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.

Issues that need to be closed to finish the upgrade from 1.8

Related to upgrading GitLab software

This label represent issues that requires fixes too be developed upstream in dependency projects