Update severity count based on dismissal reason
What does this MR do and why?
Now that Enable vulnerabilitySeveritiesCount filtering b... (#420064 - closed) • Unassigned • 16.4 • On track was merged, we can now pass the dismissal reason to the vulnerability_severities_count graphql query to properly show the counts when filtering on dismissal reason.
Related to #420065 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Notice the count cards!
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
Prerequisites
- You need an EE license
- You need to have runners enabled (See $2408961 for setting up a runner)
- Import https://gitlab.com/gitlab-examples/security/security-reports
- Run a pipeline on master
Validate
- Go to security-reports vulnerability report: http://gdk.test:3000/root/security-reports/-/security/vulnerability_report
- Filter on a dismissal reason
- Validate that the count cards update correctly now based on the results in the table
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 Lorenz van Herwaarden