Change order of unknown and info severity
What does this MR do and why?
This brings consistency in the order of the info and unknown severities in several places.
The "Unknown" severity should come after "Info".
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
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
Vulnerability Report (count, severity filter, grouping)
- Go to security report vulnerability report
- Validate that in the vulnerability count tiles, the "Unknown" severity is still last in order (after "Info")
- Validate that when clicking the severity filter dropdown, "Unknown" severity is now the last option
- Select Group By > Severity and validate that "Unknown" is the last group
New Vulnerability Form
- Go to security report vulnerability report
- Click Submit vulnerability
- Open the severity dropdown and validate that "Unknown" is the last option
Project Security Dashboard
- Go to the Security Report Security Dashboard (Secure > Security Dashboard)
- Validate that "Unknown" is the last severity in the legend
Security Policy Scan Rule Builder
- Go to Secure > Policies in the Security Reports project
- Click New Policy
- Click Select Policy in the Scan Result Policy tile
- In Select scan type dropdown, select Security scan
- Click on the All severity levels dropdown and validate that the "Unknown" option is last
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