### Summary In the [DevOps adoption MVC](https://gitlab.com/gitlab-org/gitlab/-/issues/247112), we created a table that shows the adoption of GitLab features by groups. In the MVC, the features shown in the table are: - issues - MRs - Approvals - Runners - Pipelines - Deploys - Scanning  ### Problem to solve Customers have expressed strong interest in the feature adoption table to help understand the adoption of GitLab features across their organization. This information helps them understand their ROI in GitLab by showing the breadth of adoption. It also helps formulate a case for upgrading to a higher tier of GitLab. For example, if adoption is strong, it may be worth investing more and unlocking more features for development teams. Quotes from interview with https://gitlab.lightning.force.com/lightning/r/00161000002xBeQAAU/view: > "How do I know I'm getting bang for my buck, and how do I know that my users are adopting these features?" > "When do I introduce Ultimate and at what point does that provide a value proposition?" > "Currently I keep a manual list of the features being used by teams. I build this list by going around to each team and interviewing them. Having a dashboard view of feature adoption within the GitLab UI would save me hours of time and help me keep track of how my "customers" are using GitLab." > My organization is large and we run numerous instances of GitLab. We do spot checks on "hey, if we were to consolidate your instance into mine, would there be a challenge in streamlining your instance into ours? Being able to compare the features and tiers being used in each instance would help us answer this. While the features added in the MVC are a good start, a more detailed breakdown of feature adoption would get customers closer to abandoning manual tracking mechanisms and using GitLab as the source of truth for feature adoption. ### User Application Development Director Product Manager for Enterprise Technologies As the Product Manager for Enterprise Technologies, I am responsible for providing development platforms and tooling to over 5,500 developers across the organization. When GitLab comes up for renewal, I often get asked by leadership to provide data on which parts of GitLab our teams are using. I need to demonstrate that the organization is getting value from GitLab and should continue to invest in it. ### Feature requests - Support ascending/descending column sorting so we can see all the groups that have/haven't adopted specific features - Add a total column to show the percentage of features adopted by a group - Add container and package registry adoption - For Scanning, show a breakdown of SAST, DAST, etc. - Add Terraform state ### Suggestions from PMs and customers #### Create - Keep MRs - Keep Approvals - Approval rules - Protected branches - Codeowners - Parital clone (customer request) - Commits (customer request) - GitLab LFS (customer request) - Clone (customer request) - Push rules - Protected tags - Templates (instance/group) #### Verify - Shared runner - Group runner - Keep Pipelines - Pipeline Editor * Review Apps * Browser Performance Testing * Accessibility Testing * Visual Reviews * Test coverage visualization * Test reports * Merge trains - Protected variables - Job artifacts - Pipelines for merge results #### Release - Keep Deploys - Continuous delivery - Advanced deployments - Feature flangs - Pages - Release management - Protected environments - Manual jobs #### Plan * Issues * Milestones * Iterations * Weight * Boards * Epics #### Secure - Scanning - SAST - DAST - Vulnerability management - Fuzz testing - Dependency scanning #### Package - Package registry (published) - Container registry (publish image) - Container registry (pulled image) - Private registry (package install) - Public registry (package install) #### Configure * GitLab Managed Terraform State * Terraform MR widget * GitLab Kubernetes Agent * Slack integration / chatops CI jobs * Vault integration * Auto DevOps templates in CI #### Monitor * Integrations * Alerts * Incidents * On-call schedules * Status Page #### Protect #### Manage - Compliance frameworks - Audit events(?) - Enhanced auth