Improve the order of Vulnerability-Check Criteria
Problem
The current order of Vulnerability-Check
items is a little hard to follow for the following reasons:
- The number of Approvals required is listed right next to the number of Vulnerabilities allowed. These are both number input fields and can easily be confused with each other. Also the number of approvals is currently separated from the list of approvers.
- Ideally the number of vulnerabilities allowed would be co-located with the severity levels that are considered. This provides for a more natural logical flow in the user's mind. For example, "I am allowing 5 vulnerabilities of severity Critical or High".
Proposal
Provide a more natural flow with the Vulnerability-Check criteria by re-ordering the items in the order that they will eventually be found with the future Security Policies:
- Rule name
- Security scanners
- Target branch
- Vulnerabilities allowed
- Severity levels
- Vulnerability type
- Approvals required
- Add approvers
Edited by Sam White