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://about.gitlab.com/handbook/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://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.

Related to upgrading GitLab software

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

Issues that show up in the Usability Wishlist on our direction page

Issues related to other tabs or aspects of the usage quotas view

Issues related to the pipelines tab of the usage quotas views

Issues related to the seats tab of the usage quotas views

Issues related to the storage tab on the usage quotas page

Issues related to transfer tab of the usage quotas view

Issue requesting feedback or sharing information with GitLab users

Issues related to creating users (either by a user or admin).

End-to-end user flow encompassing multiple GitLab features