Draft: Do Not Merge One-off policy to remove feature::enhancement from open issues

Description

featureenhancement was previously renamed from ~enhancement which was applied without the same rules. Due to this, Open issues in featureenhancement may not fit the definition from https://about.gitlab.com/handbook/engineering/management/throughput/#implementation

Refinements to an existing feature that is user-facing or improves the usability of existing features.

Spreadsheet with ~"feature::enhancement" issues by group

Plan

Part of gitlab-com/www-gitlab-com#9497 (closed)

• Run automation to add ~feature to featureenhancement open issues without ~feature - https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/815786068
• Run automation to remove featureenhancement open issues - https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/815786067

Open Questions

• Is there a more efficient way to review current featureenhancement issues for PMs and then bulk remove featureenhancement from un-reviewed issues?
• What should the message for communication be?