## User story As a business leader, I need to demonstrate that GitLab is being adopted by teams so I can justify renewing our contract. ## Proposal 1. Add more GitLab features to the table so that I can get more insight of which features have been adopted by each group in my organization. https://gitlab.com/groups/gitlab-org/-/epics/5019 1. [Group GitLab features by Dev Sec Ops so it is easier to view and absorb, and I can zoom in on the areas I am more interested in](https://gitlab.com/gitlab-org/gitlab/-/issues/326480) 1. Within the Dev Sec Ops grouping, organize GitLab features by stages in the software development lifecycle to zoom in even further https://gitlab.com/gitlab-org/gitlab/-/issues/323649 1. [Add an Overview section and trend graph to show the status and trend in adopting GitLab features](https://gitlab.com/gitlab-org/gitlab/-/issues/326480) ## Requirements - These improvements should be available in both the group and instance feature - Usage ping implemented to track usage of this feature at the group and instance level. For instance level, we currently only get data for DevOps Reports page views. We would need separate tracking for the DevOps Score tab and adoption tab to really understand usage of the adoption table. ## Acceptance criteria - [x] Input has been provided by product managers for each stage regarding the most important features to highlight https://gitlab.com/groups/gitlab-org/-/epics/5019 - [ ] [Input has been provided by internal stakeholders most likely to dogfood this feature](https://gitlab.com/gitlab-org/ux-research/-/issues/1363) - [x] [Feedback has been gathered from 5-10 end users that have expressed interest in this feature](https://gitlab.com/gitlab-org/ux-research/-/issues/1363) - [ ] User documentation exists and includes the use case for understanding if GitLab is being adopted - [ ] Blog post focused on the user story