Group-level activity overview: MVC

Copied from Instance-level activity overview MVC

Problem

We need to start addressing 2 key challenges enterprise GitLab customers face:

1. GitLab ROI & Value - Backward-looking justification - Understanding and demonstrating the ROI of GitLab by understanding project, group & instance-level activity (see GitHub Enterprise).
2. Transformation progress & benchmarking - Forward-looking guidance - Understanding progress of DevOps transformation and how their company compares to others in similar industries, markets, etc. Getting advice on how they can further their progress.

We plan to start by tackling 1, with 2 as the end goal.

Ultimately, we are helping our users understand and communicate how their DevOps effort metrics are impacting business value and product management (customer) value. To do this we must help them understand how to define, measure, and track business value from different points of view — and ensure that developers deliver meaningful value for the business and its customers.

Target users

• Director of DevOps / CIO - Buyer Personas
• Parker, Product Manager - User Persona
• Gabe, Engineering Director - User Persona

Proposal

MVC

Display the following metrics on the group overview page. These should be fixed to the last 90 days:

• Count of new members added to the group within the 90 day period
• Count of created merge requests in the 90 day period
• Count of created issues in the 90 day period

We can display these in a single container, like we do on the VSA page:

Table link destinations (deprecated)

• ✅Group: Group >> Group overview >> Details
• Subgroups: Group >> Group overview >> Details >> subgroups and projects tab - this is same as the above link... so may not be worth doing
• Projects: Project list view - I don't think there is a view for this one yet
• Active users: Users having "activity" like what appears on a person's Activity page.
• ✅Members: Group >> Members
• Issues created: Group >> Issue >> list - this would work if issue lists had a date range picker component
• MRs created: Group >> MR >> list - this would work if issue lists had a date range picker component
• Pipelines run: I don't think there is a view for this one yet
• Releases: nor this
• Security scans: nor this
• ✅Vulnerabilities: Group >> Security - this actually lines up coincidentally with our pre-selected date range

✅ - Link has a proper destination (I think)

In future iterations, we can show these numbers over time and call out specific features that are not being used that are part of that instance's tier (e.g. use CI).