Waiting and Blocked states now count as waiting
If your workflow mapping has a Waiting bucket, or a team uses a Blocked state, the time an item spent there used to be folded into whichever stage came just before it, so it counted as active work. It now counts as wait time everywhere. Flow efficiency on Flow Metrics and Delivery Signals can read lower for those teams, and the new figure is the corrected one. The stage breakdown, the Cumulative Flow Diagram and the Aging tab show a dedicated Waiting lane instead of hiding that time inside In Progress. The Cumulative Flow CSV export gains a Waiting column at the end, after the existing columns, so anything you already built on that file keeps its column positions. If you have never used a Waiting or Blocked state, nothing changes for you.
A view that cannot load now tells you what to do
Until now a view that could not read its data showed the raw text Azure DevOps returned, which for most people meant a code such as TF400813 and no idea what to do next. Every analytics view, every Configuration tab and every dashboard tile now shows one consistent notice: a short headline that says what went wrong, for example that your account cannot read this team’s work items, that the project or team is no longer available, or that Azure DevOps could not be reached; one line on what you can do about it; and the original technical detail kept behind a small Technical details link for whoever needs it. The notice appears in the language you chose for the hub, matching every other piece of copy on that screen. Messages already written for a specific situation, such as a licence or seat state, are unchanged, and nothing new is collected.
A brief licensing outage no longer locks anyone out
If your organisation’s access is managed by your plan and our licensing service is briefly unreachable, the hub now remembers the access decision from the last time it checked in and keeps using it, instead of falling back to an out-of-date local list that could leave people out. It only ever replays a decision the service already made, never grants anything new, and stops applying after seven days without contact, the same window your licence status already uses. Team and Business plans only; trials and Starter are unaffected.
The Privacy tab says exactly what leaves your tenant
Configuration, Privacy used to imply the extension never records names, emails or project, team and sprint names at all. It now scopes that list to usage telemetry, says that events carry your organisation ID and an anonymous user ID (your Azure DevOps user GUID, used to count active users and, on seat-limited plans, to apply your seat limit), and separately names the two things outside usage telemetry that do reach us: the administrator sign-in name captured on first hub open, with its undo window, and scheduled report subscriptions. None of this is new behaviour; all of it was already in the published privacy policy. The tab now says it too.
Related: Privacy policy
Exported charts say where they came from
PNG chart exports, the Retro Snapshot and Sprint Report share text, and the printable Executive Report now carry a quiet footer line: Agile Analytics for Azure DevOps, ado-analytics.baytekdev.com. When a screenshot or file gets forwarded on, whoever receives it can trace it back to the product. It is static text only, nothing is tracked and nothing is sent anywhere, and CSV, JSON and YAML exports are unchanged.
Smaller things you may notice
Captions, labels and other secondary text are slightly darker so they read clearly in the light theme, and locked navigation items use a proper muted colour instead of fading the whole row. Dates on Sprint Summary and Sprint Detail follow the same format as the rest of the hub and the Azure DevOps page around it, instead of always reading as US dates. The group seat rules section under Access Control says plainly that group seat rules are a Team and Business plan feature; group sync itself is unchanged.
Since our last post here
The 6.50 line shipped between this post and the last one. Your saved team comes back on every load again, even when your default project is not the project the Azure DevOps page was opened from. Team Benchmarks shows a dash, not a bold green 0/0, for a team the WIP Monitor has no data for, and explains itself when the WIP Monitor has never been set up. Delivery Signals leaves a sprint with nothing completed out of its median cycle time, sprint table, trend lines and CSV instead of counting it as 0.0 days. The Cycle Time chart’s month labels and the Retro Snapshot’s sprint dates show the calendar date the sprint used for customers whose clock is set west of UTC. Feature Analytics and Epic Analytics read in batches, keep the result for a couple of minutes so switching away and back is instant, and have a Refresh button; a Feature whose stories could not be read now says so instead of showing zeros. AI Metrics and Configuration, Readiness are translated in full, and the hub downloads only English plus your own language instead of all six on every load.
Updating
Azure DevOps updates the extension automatically, nothing to install. Everything above works with your data staying inside your Azure DevOps organisation: no PAT, no data sent to us. If a figure still looks wrong after the update, use Ask Henry in the top bar and a real person replies within one business day.
Related: Service status