Resolve "Clear Error Tracking cache on demand"
requested to merge 197320-clear-cache-after-sentry-error-update into 39825-close-issue-after-error-resolve
What does this MR do?
Note: This is based off !22744 (merged)
The only commits relevant at the time of writing are :
This clears the ReactiveCache(s) of the Sentry Issues response after we update an Sentry Issue.
Why is this needed?
When updating an issue (resolving or ignoring) we want this status to be updated on the Error Tracking list page. Without this change we are served old stale cached results.
More info here: #197320 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Closes #197320 (closed)
Edited by Sean Arnold