Labels

Issues and MRs that triage bot should not action on.

Effort tracking for a Technical Writing-related issues/MRs.

Effort tracking for a Technical Writing-related issues/MRs.

Effort tracking for a Technical Writing-related issues/MRs.

Effort tracking for a Technical Writing-related issues/MRs.

Effort tracking for a Technical Writing-related issues/MRs.

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

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

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

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

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://handbook.gitlab.com/handbook/product/groups/product-analysis/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://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification

Work that helps unblock other teams, often coming in as a request

Issues required to support release date (3rd Thursday of each month instead of 22nd)

denotes information regarding the user's journey through our tech stack

Related to the User Trust Score service

All things related to Hashicorp Vault

a project which could be outsourced

This tells the automation that the attachments in this issue have been verified not to contain confidential data. See https://gitlab.com/gitlab-com/gl-security/appsec/appsec-team/-/issues/287