Not all security scans are enabled by Auto DevOps
Summary
In a project which has Auto DevOps enabled, the Security Configuration page claims that:
All security scans are enabled because Auto DevOps is enabled on this project
when in fact the table immediately below shows that not all security scans are enabled.
Steps to reproduce
- Create a new project
- Enable Auto DevOps for the project
- (May not be necessary?) Run a CI pipeline on the default branch
- Visit the project's Security Configuration page
What is the current bug behavior?
Either it's that not all security scans are enabled by Auto DevOps, when they should, or it's that the language in the Security Configuration page is misleading/incorrect.
What is the expected correct behavior?
We should be consistent when saying what's enabled via Auto DevOps by changing the wording All security scans
to Several security scans
Relevant logs and/or screenshots
Possible fixes
Either:
- Enable all security scans when Auto DevOps is enabled; or
- Change the language/wording on the Security Configuration page
Edited by Neil McCorrison