Make DevOps adoption report more granular
Problem
The current DevOps report displays high level summary adoption metrics for groups but does not give users the ability to drill into details to understand where capabilities have (or have not) been adopted within a group.
For example, a group with 1000 projects will show has having adopted all Ops features if there is a single project that set up a runner and a CI config that deploys to an environment. This effectively hides the real state of adoption and lowers the value of the report itself.
Example use cases
- As a manager or team lead, I want to track which projects are (or are not) using GitLab CI to build/test their applications
- As an security lead, I want to identify projects that have not enabled security scans
- As an auditor, I want to identify projects missing code approvals
Proposal
Improve granularity of adoption information, covering the following:
- Number or percentage of groups/projects that have adopted each feature
- Ability to drill down to list projects/groups that have or have not adopted a feature
- Ability to sort or filter the list based on activity, for example to focus analysis only on projects that have been active the past month (this is to filter out dormant projects that may be less relevant to tracking adoption)
- Ability to export an adoption report for auditing or further analysis
Edited by Luke Stahlman