[Value Stream Analytics] Measure from issue open to issue close
Problem to solve
Currently Value Stream Analytics considers the value stream to end when a merge request is closed. However, "a unit should not equal a Merge Request but rather a unit of completed customer value. This is because many MRs can make up one unit, but what we really ought to care about and encourage is the throughput for units of value -- which are typically represented as Issues." (from @gweaver) In other words, Value Stream Analytics should consider the value stream to end when an issue is closed (not a merge request).
Proposal
There is a new default stage called "Closed" that appears below "Production". It measures time from production to deployment to issue closed. This is effectively "lead time".
Out of scope
- The "Total" stage is being eliminated, otherwise it should measure time from issue open to issue close.
- Lead time (which replaces "Total") and cycle time already measure to issue close.