Related to upgrading GitLab software

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 related to unit testing of GitLab code

Label to tag type support requests for the Test and Tools Infrastructure Team

label to tag support requests for Test Platform sub-department

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

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

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

Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

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

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

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

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

(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 developing or revising a few sentences

(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 fixing a single misspelling or adding a punctuation

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.

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