Render agent plan widget only when AI planning is enabled

Vanessa Ottorequested to merge
608883-fe-conditionally-render-work-plan-widget-and-plan-cta-based-on-ai-enabled-flag into master

What does this MR do and why?

Stacked MR — this MR targets 608883-fetch-agent-plan-via-standalone-query (!251768 (merged)), not master. !251768 (merged) splits the agent plan fetch into its own query so namespaceWorkItem stays under the GraphQL complexity cap; this MR builds the aiPlanningEnabled field + Plan CTA on top of it. Please review and merge !251768 (merged) first. The diff shown here is only the incremental change on top of the refactor.

Render agent plan widget only when AI planning is enabled

Backend counterpart: !249644 (merged)

Related to #608883 (closed)

References

Screenshots or screen recordings

Viewport size Before After
xs (<576px) Screenshot_2026-08-20_at_15.44.12
sm (>=576px)
md (>=768px)
lg (>=992px)
xl (>=1200px) Screenshot_2026-08-20_at_15.44.31

How to set up and validate locally

  1. Enable Feature Flag workplan
  2. Disable Feature Flag work_item_features_field
  3. Create a new work item of type issue or task
  4. Click "Plan" to add the SDD features to the work item, it also removes the 'Plan' button
  5. Enable Feature Flag work_item_features_field
  6. Repeat Steps 3 + 4
  7. If possible, open a work item which had a workplan before you tested this branch. The workplan is still there without an extra click on the 'Plan' button
  8. Make sure the "Plan" button does not exist on non-supported work item types, e.g. an epic - the BE takes care of this logic though, no code for this was added within this MR

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #608883 (closed)

Edited by Vanessa Otto

Merge request reports