Project Health Analytics: MVC
Overview
Customers (internal and external) have expressed interest in having a high-level overview of a project's health - engineering managers who'd like to stay on top of a project's current status need to use a number of sensing mechanisms to feel like they're on top of the current state of the codebase. Instead, we should condense health metrics into a single view.
Proposal
Implement the design in #196177:
- Display cycle time, merged MRs, opened issues, total number of issues with ~bug label, new/closed issues with ~bug label.
- Fixed to past 30 days.
- Cycle time should tie with #21863 (closed) and Value Stream Analytics.
- Question-mark help icons display the definitions below.
Definitions
- "Cycle time": "Time from MR open to MR merge of all Merge Requests opened and merged in the time period." Note: This would consider "all Merge Requests merged in the time period", regardless of when they were opened, except that Value Stream Analytics limits the perspective to those also opened in the time period.
- "MR throughput": "Number of Merge Requests closed in the time period."
- "Issue velocity": "Total weight of the Issues closed in the time period."
- "Code coverage": "Average code coverage for each type of pipeline (frontend/backend/etc) currently. Limited to types run in the time period."
- "Bugs - total": "Number of Issues with a label
bug
orBug
currently." - "Bugs - opened vs closed": "Number of bug Issues opened in the time period versus the number closed in the time period."