## Purpose Retire the legacy issue framework, eliminate unused feature-flagged code paths, and reduce maintenance cost while preserving current user workflows. ## Objectives 1. Inventory all legacy issue feature flags still present in the monolith. 2. Document dependencies, owners, and deprecation risks for each flag. 3. Produce and execute a phased removal plan with milestones, rollout gates, and rollback steps. 4. Ship replacement experiences or blocking capabilities so users remain unblocked. ## Current State Analysis Before we can remove legacy issue code, we need to support issue types that are still using the legacy framework: | Issue Type | Status | Migration Complexity | Missing to unblock removal | | ------------------------ | --------------------------- | -------------------- | ------------------------------------- | | Incidents | On hold | High | Additional specialized widgets needed | | Service Desk Issues | On hold | Medium | Base work item type POC exists | | Test Cases | Backend migrated, UI legacy | Medium | UX | | Requirements | Same as Test Cases | Medium | UX | | Objectives / Key Results | Beta (dogfood paused) | Small | Product decision on OKR sunset vs. GA |