Pass dismissal reason to vulnerability_severities_count graphql query
As a follow-up to Filter by dismissal reason on the Vulnerability... (#408983 - closed) • Samantha Ming • 16.3, the vulnerability severities counts should be updated when filtering on dismissal reason too.
Implementation plan
- update
ee/app/assets/javascripts/security_dashboard/graphql/queries/vulnerability_severities_count.query.graphql
to accept dismissal reason variable - update specs accordingly
Verification steps
- Go to security-reports vulnerability report: https://gitlab.com/gitlab-examples/security/security-reports/-/security/vulnerability_report/?state=ACCEPTABLE_RISK,FALSE_POSITIVE
- Filter on one or more dismissal reasons
- Verify that the severity counters sync properly with the amount of vulnerabilities in the table. Before, when any dismissal reason was selected, the severity counters would shown the amount of dismissed vulnerabilities (regardless of dismissal reason)
Edited by Lorenz van Herwaarden