Legacy Vulnerability check should only be required for Critical, High, Unknown
Summary
From a slack thread (internal link).
The introduction of new approval policies accidentally modified existing approval rules to trigger for a vulnerability of ANY severity instead of only Critical, High, and Unknown.
Steps to reproduce
Pre-existing vulnerability checks will have changed to "all levels", although
The hover-over in the MR still says Critical, High and Unknown.
Example Project
What is the current bug behavior?
Approvals are required for findings of any severity.
What is the expected correct behavior?
Approvals are required only for Critical, High, and Unknown.
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)