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

Request for support by the Test and Tools Infrastructure team

🤔Issues relating to trials (owned by the Conversion group)

A meta issue listing other issues which require triaging

Issues which have a question that needs to be answered before they can be triaged (added to a milestone)

Describing introductions of or changes to issue triage policies in this project

Items that belong to the validation track only | https://about.gitlab.com/handbook/product-development-flow/

Items that belong to the build track only | https://about.gitlab.com/handbook/product-development-flow/

See https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/1202#note_877272383

Issues related to the To-Do List feature: https://docs.gitlab.com/ee/user/todos.html

Issues that need to be scheduled for a future release

Feature vision in Plan stage: &781

This issue or epic needs a threat model

The threat model for this issue or epic is done