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

Agile Analytics 6.81.0: More exact numbers and clearer labels across your views

Time per stage now counts work finished on the last day of a sprint and after it, Quality & Rework counts late finishers in its oldest sprint, and Next Sprint Planning says when your last sprint has ended. The local AI connector’s forecast starts from the same 6 sprints as the screen.

  • #release notes
  • #6.81
  • #6.81.0
  • #azure devops
  • #flow metrics
  • #quality
  • #local ai connector

Time per stage adds up

A finished work item’s stage time is measured up to the moment it was finished, including work on the last day of the sprint and, for an item closed after the sprint, the time after it. The stages now add up to the item’s lead time. Stage Time Breakdown in Flow Metrics, and Time in review in Quality & Rework, Retro Snapshot and the Exec Report, can read slightly higher for teams that finish work on the last day of a sprint or later.

Sharper sprint numbers

In Quality & Rework, the oldest sprint in the table also counts work items that were left in the sprint before it and finished in its first days, so Reopen rate for that sprint and the total above the table can change for teams that close work a few days late. Throughput says how many of its items were closed after the sprint ended, in Retro Snapshot, Sprint Detail, Sprint Capacity and the copied sprint reports; the totals are unchanged.

Next Sprint Planning knows when your sprint has ended

When your team’s last sprint has ended and no next sprint exists in Azure DevOps yet, Next Sprint Planning says so and asks for the next sprint to be created. Its sprint dates are written in your display language.

Your assistant gives the number on your screen

The local AI connector’s forecast starts from the 6 newest finished sprints, the sprints the Monte Carlo view and the Dashboard start from. Its sprint summary also says how many delivered items were closed after the sprint ended.

Related: Local AI connector guide

Clearer labels

Multi-Team Aging names each count by the state the work items are really in, and says when open items are in a state your Workflow Mapping does not cover. Delivery Signals, Team Benchmarks, User Metrics and the Exec Report show a dash where nothing was measured, and the Dashboard’s Sprint Velocity table shows Commitment with the same one decimal as Flow Metrics and Sprint Summary. More dates and labels follow your display language, and Org Hygiene describes stale work items more precisely.

What you need to do

Nothing; Azure DevOps updates the extension automatically. These changes reach you with 6.82.0, and local AI connector users on @latest get 6.82.0 automatically.

Related: 6.82.0: Cycle time that matches across views · 6.80.0: Quality numbers in your reports · 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 →