Version 6.1 closes the loop between your Azure DevOps process and the metrics on your dashboard. Custom workflow states are now auto-detected from your project — no more typing them by hand. A new Flow Efficiency view shows where your cycle time is actually being spent (active work vs. queues). Service Level Expectations let you set "X% of <type> finish in Y days" targets that surface as green / amber / red badges right on the Dashboard. Patch releases through 6.1.2 add lenient state-name matching, a heuristic fallback for fresh installs, and a clearer diagnostic when work-item history is too thin to measure.
Custom states auto-discovered
Workflow Mapping now reads your project's actual states from Azure DevOps. Any custom state your team uses — "Awaiting QA", "Stakeholder Sign-off", or anything else — appears in the dropdown automatically. You no longer have to type state names by hand or risk a typo breaking your cycle-time calculation.
Cycle Time preview inside Workflow Mapping
A new panel under each project mapping shows exactly which of your states count toward cycle time (active and queued) and which are excluded (pre-work like New or Approved). The mapping is the cycle-time configuration — there is no separate place to look.
New: Flow Efficiency view
A new view under Measure → Flow Efficiency shows the percentage of cycle time spent actively working versus waiting in queues, broken down per state, with a top-25 items table sorted by cycle time. Healthy knowledge-work teams typically run between 15% and 40%.
New: Service Level Expectations (SLEs)
Configure per-item-type cycle-time targets under Configuration → SLEs — for example, "85% of User Stories finish in 14 days". The Dashboard shows a green / amber / red badge for each enabled SLE so the team can see at a glance where flow is on track and where it is not.
"How is this calculated?" tooltips
A small (?) icon next to the Cycle Time and Flow Efficiency headers explains the math and links straight to Workflow Mapping, so anyone reading the chart can answer the inevitable "where does this number come from?" question without leaving the view.
Readiness check covers Workflow Mapping
Configuration → Readiness now flags projects without a workflow mapping configured, so cycle time, lead time, and flow efficiency cannot silently report zero on a project that was never mapped.
Patches: 6.1.1 and 6.1.2
Two patches landed after 6.1 to make Flow Efficiency more forgiving in real-world conditions.
- 6.1.1 — Flow Efficiency now matches state names with substring matching instead of strict equality, so a state like "In Progress (Dev)" matches a token of "in progress". A heuristic fallback also recognises common ADO state names (Active, Closed, Resolved, Code Review, etc.), so the view works out-of-the-box on a fresh install before any Workflow Mapping is configured.
- 6.1.2 — When Flow Efficiency cannot measure cycle time, the empty-state message now tells you why with the right diagnostic instead of always pointing to Workflow Mapping. Three cases are distinguished: no items in the window, items still in flight (no done state yet), and items with thin state-change history (typical of imported, migrated, or scripted data).
Bug fixes & polish
Smaller fixes that landed alongside 6.1.
- Dark mode is now Primer-aligned across Configuration tabs, Org Hygiene, Sprint Capacity, and Sprint Summary.
- The Configuration left-nav active state uses a neutral grey background with a purple accent rail (ADO-native palette, brand purple kept for accents only).
- WhatsNewDialog redesigned: bigger card, dedicated trial-extension callout, and scrollable on small viewports.
Update to 6.1.2 from the VS Marketplace. Already installed? The What's New dialog will re-fire automatically on first load after the upgrade, so the team will see what changed without anyone needing to share a link.