Skip to content

Update severity count based on dismissal reason

Lorenz van Herwaarden requested to merge update-severity-count-frontend into master

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
Screenshot_2023-09-18_at_11.24.08 Screenshot_2023-09-18_at_11.23.34

How to set up and validate locally

Prerequisites

  1. You need an EE license
  2. You need to have runners enabled (See $2408961 for setting up a runner)
  3. Import https://gitlab.com/gitlab-examples/security/security-reports
  4. Run a pipeline on master

Validate

  1. Go to security-reports vulnerability report: http://gdk.test:3000/root/security-reports/-/security/vulnerability_report
  2. Filter on a dismissal reason
  3. 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.

Edited by Lorenz van Herwaarden

Merge request reports

Loading