Severity counts do not update after bulk dismissal of vulnerabilities on Project Security Dashboard
Summary
When dismissing one or more vulnerabilities in the project security dashboard, the counts by severity displayed at the top of the page do not update.
Steps to reproduce
- Navigate to the Project Security Dashboard for any project with undismissed vulnerabilities
- Leave the Status Filter in it's default state (Detected + Confirmed)
- Observe the counts displayed above the vulnerability list
- Dismiss >= 1 vulnerability through the bulk dismiss option on the dashboard
- Observe the counts displayed above the vulnerability list, note that no counts have changed
Example Project
What is the current bug behavior?
The counts do not update to reflect the dismissal event.
What is the expected correct behavior?
What is displayed will reflect the state after the vulnerability/vulnerabilities have been dismissed.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
-
The ee/app/assets/javascripts/security_dashboard/components/selection_summary.vue
seems to emit avulnerability-updated
when the dismiss action is successful. However we do not react on thatre-fetch
the vulnerabilities. In theee/app/assets/javascripts/security_dashboard/components/vulnerability_count_list.vue
we need to react to this event and refetch the statistics.
Edited by Savas Vedova