Release Notes · November 22, 2026 · 3 min read · By Baytek

Agile Analytics 6.82.0: Cycle time that matches across views, and work in unmapped states now in view

With the default 6 sprints, Flow Metrics and Delivery Signals show the same Median Cycle Time as the Dashboard, Aging & Blocked shows open work items in unmapped states, and work moved into a sprint after it ended is no longer counted as added scope.

  • #release notes
  • #6.82
  • #6.82.0
  • #azure devops
  • #cycle time
  • #flow metrics
  • #aging

Cycle time that matches across views

Flow Metrics and Delivery Signals take one median over every finished work item in the chosen sprints. With the default 6 sprints it is the P50 the Dashboard and the Cycle Time view show for the same team. Avg Lead Time on Flow Metrics is one average over the same items (the Dashboard shows the median lead time, so those two differ). Both figures can change, most for teams whose sprints finished very different numbers of work items, and the Delivery Signals card’s colour follows the new figure. The per-sprint rows keep each sprint’s own figures.

One clock start for Flow Efficiency and Service Levels

When a work item waits in a state mapped to In Progress whose name says it waits, such as "Ready for Dev", before work starts, the clock now starts there, as on the Cycle Time view, and that time counts as waiting. For teams whose work waits like this, Flow Efficiency can read lower wherever it is shown, including the Dashboard’s "Since you were last here" card, and Service Levels count more days per item.

Work in unmapped states, now in Aging & Blocked

Open work items of the current sprint (and those still open from the previous one) in a state your Workflow Mapping does not cover appear in a "Not mapped" lane, with their own state, their days in that state and their days in flow. They appear in the Blocked tab only when they carry a blocked signal. States Azure DevOps files as finished or removed stay out.

Related: Workflow Mapping guide

Sharper sprint and forecast numbers

A work item that was not in the sprint while it ran and was moved into it after the sprint’s last day is no longer counted as added, wherever added scope and scope churn are shown, such as Sprint Summary, Cumulative Flow, Retro Snapshot and the Exec Report. Sprint Summary lists such items on their own line; they still count in the sprint’s total and, when done, in its throughput. The Forecast Scorecard scores a forecast once your sprints reach the end of its window, allowing a gap of a few days such as a weekend; an earlier result for a window that ended outside your sprints goes back to "not scored yet", so the hit rate above the list can change. Where your Workflow Mapping has more than one done state, Monte Carlo by weeks counts a work item in the week it moved into a done state, so weekly counts and the forecast built on them can move for those teams.

Clearer text

Configuration, Access Control shows your licence’s seat count or that there is no seat limit, and dates on the License, Access Control, Readiness and Support tabs name the month. How These Metrics Work names more of the rules that can change a number, and the Epic roadmap lists unfinished Epics with no plan and no forecast date yet under "No landing date" (it was "Unscheduled").

Your assistant follows the same rules

The local AI connector 6.82.0 answers flow efficiency with the same clock start, and its sprint summary leaves out of added scope the work items moved into the sprint after it ended.

Related: Local AI connector guide

Also in this release

Everything announced for 6.81.0 reaches you with 6.82.0: time per stage that adds up to lead time, sharper sprint numbers in Quality & Rework, Throughput that says how many of its items were closed after the sprint ended (the totals are unchanged), Next Sprint Planning that knows when your last sprint has ended, and clearer labels.

Related: 6.81.0: More exact numbers and clearer labels

What you need to do

Nothing; Azure DevOps updates the extension automatically. Local AI connector users on @latest get 6.82.0 automatically.

Related: Full release history

Compare your Azure DevOps reporting options before you commit

See how built-in ADO reporting, Power BI, and Marketplace extensions stack up, then start the 30-day trial to evaluate the extension path inside your own organisation.

Related reading

Find our articles faster: add Agile Analytics as a preferred source in Google Search.Add preferred source →