Release Notes · October 14, 2026 · 3 min read · By Baytek

Agile Analytics 6.60: Started and End dates in Feature and Epic Analytics, and work in progress that counts only real work

Feature Analytics and Epic Analytics now show when work started and when it ends, and each Epic roadmap card shows the same dates. Removed items no longer count as work in progress, and a reopened item in Aging & Blocked is aged by the days it was worked, not the days it sat closed. Cycle Time is unchanged.

  • #release notes
  • #6.60
  • #feature analytics
  • #epic analytics
  • #work in progress
  • #aging
  • #azure devops

Started and End dates in Feature and Epic Analytics

Feature Analytics and Epic Analytics have two new columns after State. Started is the date the first child item became active, so you see when work really began, not when the item was created. End is the date the item was delivered. If it is not delivered yet, End shows its Target Date, and for Epics without a Target Date it shows our forecast. Each End value says which one it is: Delivered, Planned or Forecast.

  • Each card on the Epic roadmap shows the same two dates, for example “Started 4 Jul 2026 · Planned 15 Dec 2026”. The table and the roadmap use the same rule, so they always agree.
  • Removed child items are left out when Started is worked out. An item with no children uses its own start date. A dash means there is no start date to show.
  • No other figure in these views changes, and the dates come from data the extension already reads.

Removed items no longer count as work in progress

An item that was started and then set to Removed kept counting as work in progress. The WIP Monitor, the WIP chart on Flow Metrics and the Dashboard WIP figure now leave it out from the moment it was removed. If your team removes work after starting it, these figures can go down. Before it was removed, the item still counts for the time it was really in progress.

Reopened items are aged by the time they were worked

An item that was closed and then reopened was aged in Aging & Blocked as if the closed period were work. An item that was active for 5 days, closed for 20 days and reopened 2 days ago showed 27 days. It now shows 7, the days it was actually worked. Multi-Team Aging and the aging risk in Exec Report count it the same way.

  • Only items that were closed and then reopened change. Every other item keeps exactly the age it had.
  • Cycle Time is unchanged. It still measures from the first start to the final finish, the same way Azure DevOps does.

Dashboard widgets are easier to read on the dark theme

Widget labels, team names and secondary text on your Azure DevOps dashboards now follow the Azure DevOps theme, so they are easy to read on the dark theme.

What you need to do

Nothing is required. Azure DevOps updates the extension automatically. If a figure looks wrong after the update, use Ask Henry in the top bar. Work-item content stays in your Azure DevOps tenant.

Related: Service status

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 →