Refetch work item in board drawer after a card move

Coung Ngorequested to merge
561257-board-drag-stale-drawer into master

What does this MR do and why?

Refetch work item in board drawer after a card move. This fixes a customer reported bug in #561257 (closed)

Board cards are fetched as GraphQL Issue objects, while the detail drawer fetches the same record as a WorkItem. Apollo normalizes those into two separate cache entries, and the move mutation only refreshes the Issue one. The drawer's query is cache-first, so reopening it after a drag served stale state and labels.

Evict the matching WorkItem entry after a move, so the drawer's next query misses the cache and refetches from the server.

Changelog: fixed

References

Screenshots or screen recordings

How to set up and validate locally

  1. Go to a board and set up status lists
  2. Click on an issue in one status list to open it in a drawer, then close the drawer
  3. Move the issue to another status list, then open it in a drawer to confirm the status has been updated

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 #561257 (closed)

Edited by Coung Ngo

Merge request reports