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

Agile Analytics 6.78.0: Aging flags an item only once it is older than 3 days

Aging & Blocked counts an item as "over p85" only once it is older than your team’s p85 and also older than 3 days. Forecasts now say how many finished sprints they are based on, and more views show a notice when some Azure DevOps data could not be loaded.

  • #release notes
  • #6.78
  • #6.78.0
  • #azure devops
  • #aging
  • #forecast
  • #monte carlo

Aging flags an item only once it is older than 3 days

On Aging & Blocked, an item counts as "over p85" only once it is older than your team’s p85 and also older than 3 days. When p85 is under 3 days, the header line says so. The Exec Report’s count of older open items, Sub-teams and AGAN AI use the same rule. A p85 of 3 days or more, the p50 line and the fixed bands work as before.

What this means for your numbers

A team whose p85 is under 3 days will see fewer items flagged "over p85" on Aging & Blocked, in the Exec Report’s count of older open items, in Sub-teams and in AGAN AI. A team whose p85 is 3 days or more sees the same items flagged as before. No forecast number changes.

Forecasts name their sprints

The Dashboard forecast tiles and the Exec Report (on screen, printed and shared) say how many finished sprints the forecast is based on, as the Monte Carlo view already does. The local AI connector states its sprint count with each forecast.

Improvements

Aging & Blocked, Live Stats, Monte Carlo, Cumulative Flow and the Exec Report show the same notice as the Dashboard when some Azure DevOps data could not be loaded. The printed Exec Report carries it too, and Live Stats shows the real numbers again on its next load. A setting changed in one browser tab is kept when another open tab saves something else. Live Stats remembers its Sort choice and SLE Violations its Sprints choice. User Metrics shows a loading state until its data is ready, and in Sprint Summary, "Teams at a glance" says "No sprints found" for a team without sprints. In Configuration, for people who cannot save, Item Types and Workflow Mapping show their controls disabled, and the Microsoft Teams card says at once when a webhook address cannot be reached, and which addresses work. Dashboard widgets pinned in Azure DevOps follow the same rules as the hub, so a pinned figure follows these changes too, and the Work item aging chart is announced by its title to screen readers. The Dashboard and views with several teams make fewer requests when they first open. On Flow Metrics, AGAN AI can now see the view’s flow efficiency figure; the "What we send" list shows it like every other number.

What you need to do

Nothing; Azure DevOps updates the extension automatically. If Aging & Blocked shows fewer items "over p85" than you remember, check the header line: when your team’s p85 is under 3 days, it says so.

Related: 6.77.4: Flow efficiency reads the same on every view · 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 →