Skip to content

Fix caching issue on vulnerability report

David Pisek requested to merge 411266-filtered-vulnerability-report-does-not-get-updated-when-a-vulnerability-gets-mutated into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Disable caching vulnerabilities on vulns report

This fixes an issue where the vulnerabilities report would not update when a vulnerability's state changed. This was due to the GraphQL query being cached and not updated after a mutation.

Changelog: fixed EE: true

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

  1. Go to this verification project
  2. Set the "Status" filter to "Confirmed"
  3. Set the "Status" filter back to "All statuses"
  4. Chose a (or multiple) vulnerability that does not have the "confirmed" status and select it by clicking on the checkbox
  5. Change the status to "Confirmed"
  6. Set the "Status" filter to "Confirmed" again
  7. The vulnerabilities that had their status changed are not showing up
  8. Do a full page refresh - now they do show up

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #411266 (closed)

Edited by David Pisek

Merge request reports