[Value Stream Analytics] Merge Requests should be aggregated by Issue
Problem to solve
Continuing from a conversation with @gweaver in #21863 (comment 312272174)...
Conflating Issues with MRs in [Value Stream Analytics] feels really misleading unless we are aggregating time coding, etc across all MRs associated to a given issue.
In other words, Value Stream Analytics shows issue data data for some stages, and merge request data for others, and we must normalize that data to accurately represent the value stream. For example, if a single issue has 3 merge requests associated with it, then it isn't accurate to average the time required for those 3 merge requests. It is accurate to sum the time required, because the sum represents the underlying issue.
Proposal
TBD, possibly:
- Aggregate data by issue
- Only show data for complete issues?
- Where stages involve merge requests, calculate using the last merge request against the issue.
Edited by Dan Jensen