6.59.4: workflow mapping is safer and clearer, and dashboards load faster
Saving Workflow Mapping is protected. If another admin saved changes after you opened the page, your save is stopped with a clear message and nothing is overwritten. Workflow suggestions are now shown only to admins, name the project they are about, and first-time setup only includes states that exist in your project. Existing mappings are not changed, and your numbers are unchanged.
- Configuration → Workflow Mapping marks an entry that is not a state in your project’s current process, so you can see at a glance what applies to your workflow. Nothing is changed for you.
- Cycle Time, Aging & Blocked and Cumulative Flow now tell you when your work item history contains states that are not mapped, with a link to Workflow Mapping. Cycle Time also shows how many items had no recorded start and explains how cycle time is measured.
- Dashboards load faster because the same data is no longer requested several times. First-time setup shows its progress while it reads your workflow, and boards that Azure DevOps reports as out of date are no longer used to order stages.
6.59.3: Aging & Blocked follows your real workflow, and widgets can pick a team from any project
Aging & Blocked drew a lane for every stage in your workflow mapping, including stages your project does not use, so a team working New, Active, Resolved, Closed saw empty lanes such as “Committed”, “Ready To Test” and “Ready To Review”. The chart, the stage list under its title and Aging Trend by Sprint now show one lane for each in-progress state your team really uses, in the order of your team’s board. A team with more than eight in-progress states keeps grouped lanes so the chart stays readable. Days in flow, the p50 and p85 lines and “over p85” are unchanged.
- On narrower screens, the item list in Aging & Blocked could be wider than its card. The page then scrolled sideways and cut off the left edge of every card. The rows now fit their card and wrap onto a second line when space is tight.
- In a dashboard widget’s Configure panel, the team list only covered your first five projects, so in larger organisations the dashboard’s own project could be missing. It now lists every project, starting with the dashboard’s own. Picking a team also updates the preview straight away, where it used to show “Select a team” until you saved.
6.59.1: teams with no sprints, and one name for cycle time
On the Dashboard, a team with no sprints selected in Azure DevOps saw “We couldn’t find any completed items” and a prompt to verify Workflow Mapping, although the mapping was fine. The Cycle Time card and the Cycle Time view now say the team has no sprints yet and show where to select them: Project settings → Team configuration → Iterations. Teams that have sprints see no change.
- Flow Metrics called its cycle-time figure “Avg Cycle Time” while Delivery Signals called the same figure “Median Cycle Time”. Both now say “Median Cycle Time”, the average of each sprint’s median cycle time. The numbers are unchanged.
- In the Flow Metrics and Delivery Signals CSV exports, a sprint with nothing committed, or with no flow data, showed 0% for commitment reliability, carryover or flow efficiency, where the views show a dash. Those cells are now empty, so a spreadsheet no longer reads them as a missed commitment.
Exec Report: a one-page summary you can share
Exec Report now opens with a one-page summary for leadership: a status (On track, Watch or At risk), an 85% forecast of how many items will finish in the next four weeks, the delivery trend over the last six sprints, the main risks (carryover, scope churn, items aging past the usual cycle time, bugs opened versus closed) and DORA figures when your pipelines provide them. Detail for each team follows on the next page.
- Share saves the summary as a PDF, copies it, or opens an email draft in your own mail app.
- The summary is built in your browser and is not sent to us.
- Scheduled Reports in Configuration has been removed, together with the emailed report it set up, which was delivered through our service. For figures on a regular schedule, the Delivery Digest pipeline runs in your own Azure DevOps. Data & Privacy now lists two things that reach us instead of three.
The Sprint Forecast widget is free for every organisation
The Sprint Forecast dashboard widget shows how many items a team is likely to finish next sprint, at 85% and 50% confidence. It is now free for every organisation, with or without a trial or subscription. Add it to any Azure DevOps dashboard from the widget catalog under “Agile Analytics”. The other Agile Analytics widgets and the extension itself still need a trial or a subscription.
Commitment reliability counts only your own team
In sprints shared by several teams, which is the Azure DevOps default, commitment reliability counted other teams’ items still in the sprint as work your team committed to and then moved out. Reliability read too low, and moved-out and carryover too high. These figures now count only your own team’s work, so affected teams will see reliability go up and carryover go down, including in Exec Report. Saved settings are unchanged.
AI Metrics reads GitHub’s current Copilot reports
GitHub retired its older Copilot metrics API in April 2026. Since then AI Metrics, the AI Adoption widget and Test Connection showed a misleading “not enabled” message, and AI Metrics showed only sample data. They now read GitHub’s Copilot usage reports for the latest 28 days, and error messages name the actual problem, such as an invalid token or a missing permission. Chat active users shows 0 because GitHub’s reports have no daily figure for it.
- AI Metrics saved the sample report as if it were your data, and AI Impact then read it. Only live reports are saved now. Anything already saved is left as it is.
Work item types and workflow states are detected more accurately
“Auto-detect from ADO” in Configuration → Item Types now follows Azure DevOps’ own work item categories, so renamed and custom requirement and bug types are picked up correctly. On projects using the Basic process, Issue is detected as Planned Work rather than Bug. Auto-detect only fills in the form: nothing changes until you press Save Item Types.
- New Scrum projects now count the Committed state as In Progress, because work in Committed has started. If your Workflow Mapping lists a state under Queued that Azure DevOps treats as In Progress, a notice offers to move it with one click. Nothing changes until you press Save changes.
- On projects using the Basic process, the Setup readiness check, the Sprint Alerts pipeline and “Reset to defaults” on Item Types now include Issue when you have never saved a work item type list. Lists you have saved are used exactly as before.
Smaller changes
Smaller changes in the same release.
- The single-team What-if forecast assumed a two-week sprint, so teams on one-week or three-week sprints saw a scenario that disagreed with the forecast above it. What-if now uses your team’s real sprint length.
- Configuration now asks before you leave the DORA Metrics, Epic, Access Control, Enterprise and Copilot tabs with unsaved changes, and before you switch project on the Enterprise tab.
- The Team Health widget’s name is readable in the dark theme.
- The last English text on translated views (Process Behavior metric names, the Delivery Signals trend range and two Dashboard labels) is now translated.
What you need to do
Nothing is required. Azure DevOps updates the extension automatically. If you used Scheduled Reports, set up the Delivery Digest pipeline in Configuration for a regular summary, or share Exec Report from the Share menu. 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