v2.4.2 focuses on trust and readability: sprint numbers now align more clearly with mapped workflow stages, cycle-time outliers are guarded more aggressively, and multi-team selection is easier at enterprise scale.
What's New in v2.4.2
- Current Sprint summary was redesigned with clearer labels: Total Items, Completed, Open, Reliability.
- Workflow Stage Breakdown now appears in the sprint card and is calculated directly from saved workflow mapping.
- Each stage card now has mapped-state hover help so users can see exactly which ADO states are counted.
- A dedicated New stage now appears before Queued to avoid early-state ambiguity.
- Queued defaults and suggested mapping now include New, Approved, and Committed.
- Multi-Team Scope now supports cross-project team selection with separate browse and selected-scope panes.
- Agile Coach includes a dedicated Multi-Team Aging page in navigation.
Cycle Time Data Quality Improvements
This release adds additional data hardening around workflow history timestamps to prevent malformed or sentinel values from polluting cycle calculations:
- Workflow update revised timestamps are sanitized before being used as state events.
- Invalid or extreme start/end timestamps are excluded from cycle and lead-time computations.
- When report-level cycle values are invalid, sprint view falls back to valid completed-item timestamps for p50/p85 display.
Why This Matters
- Teams can explain sprint numbers confidently without state-definition confusion.
- Coaching and leadership views stay credible even when historical timestamp quality varies.
- Large organizations can scope analysis across many teams/projects with fewer clicks and less noise.
Operational Notes
- No migration is required.
- Existing mappings continue to work.
- To apply new queued defaults to existing mappings, use Configuration → Workflow Mapping → Use Suggested on Queued.