Fixed work item subscriptions to prevent invalidating cache
What does this MR do and why?
Currently, when updating assignees, due date, or status on the work item, we have a query that refetches the work item right after a successful mutation response. This is caused by subscriptions that have a different shape from work item query which leads to cache invalidation.
This MR updates the shape of the subscription response to match the query and prevent refetching.
Screenshots or screen recordings
Before | After |
---|---|
before | after |
How to set up and validate locally
- Enable the work items feature flags
Feature.enable(:work_items) Feature.enable(:work_items_mvc_2)
- Visit any work items such as
http://127.0.0.1:3000/groups/flightjs/-/work_items/2
- Update the assignees, due date, or status.
- Check the
Network
tab: there should be noworkItem
query calls afterworkItemUpdate
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Natalia Tepluhina