Remove subscribed key from epic initial data
What does this MR do and why?
See #357986 (closed)
When loading the epic detail page, a query across all associated notes is performed to check if the current user is subscribed to the epic.
This appears to be no longer used to bootstrap the subscribed
component in the right sidebar, which issues an asynchronous request to the GraphQL API to get the same data. Embedding this data in the page adds to page load duration that increases with the number of notes on the epic. It has been observed to be as high as 150ms.
This change removes this from the page. A feature flag is included for safety.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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.