Issues that will be not handled

Related to the Work Items feature

Items related to epics migration that should be completed prior to internal rollout.

Items related to migrating issues to work items that should be completed prior to any internal rollout.

Must be addressed prior to rolling the new experience out to self-managed users.

Must be completed for epics GA rollout.

Must be completed for GA rollout of issues

These are items which are not GA-issues blockers but must be addressed as P1 post GA-issues.

First priority after both issues and epic work items are GA. Does not block any rollout.

Non-blocking work items updates that are not top priority after migration.

Applied when closing incomplete work because it is decided that no more will be done on an issue or epic.

This is a security issue that is ready to be deployed but awaiting a security release

Issues that are blocked until another issue has been completed https://handbook.gitlab.com/handbook/product-development-flow/#description-5

Merge request is deployed to the canary environment.

Applied after all MRs have merged and the issue has been verified if necessary https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-3-launch

Ideate solutions to well-defined customer problems https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-3-design

Was not advanced beyond the current version (experimental or beta). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html

Issues for features that are being enabled through a separate feature flag rollout issue