6.58.4, 8 October: forecast chart spacing, scorecard window label, Configuration saves, Aging lane label
The Monte Carlo distribution charts left out outcomes that never occurred, so bars that were several items apart sat side by side. Those outcomes now stay on the axis at 0%, so each bar sits at its true distance, on the “How many?” and “When will it finish?” charts and on the all-teams mini charts. Only the spacing changed: the numbers, percentiles and exports are the same.
- Forecast scorecard: a forecast whose window has passed but cannot be scored yet now says “window closed” with the date, followed by “not scored yet: no sprint data covers this window” instead of “window open until”. Window dates also showed a day early for viewers west of UTC and now show the correct day.
- Configuration: Save now clears the “You have unsaved changes” banner and shows “Saved” on every tab, and leaving the tab no longer asks whether to discard changes you already saved. This had affected Configuration since 6.57.0.
- Aging chart: the “Ready To Test” lane header no longer appears twice. Which items sit in each lane and the numbers are the same. This had affected the Aging chart since 6.52.0.
6.58.3: sprints without dates on the Dashboard, and a calmer export notice
In a new Azure DevOps project the first sprints have no start or end date. On the Dashboard, the Sprint Burnup card read “Day NaN of NaN” for such a sprint and the Current Sprint card showed “? – ?”. Sprint Burnup now shows the same “has no dates yet” message as Cumulative Flow, with the steps to set the dates in Azure DevOps Boards → Iterations, and the Current Sprint card reads “No dates set yet”. Sprints that have dates look exactly as before.
- When Export Sprint CSV has nothing to export, “There is nothing to export yet…” now appears in a grey notice instead of the red error box, because nothing went wrong. A real failure still shows in red.
- “View all release notes” in What’s New and in Help & Support opened our blog. It now opens this release notes page.
- The What’s New pop-up appears once for 6.58.3 and covers the changes from 6.58.0 to 6.58.3.
6.58.2, 7 October: Export Sprint CSV works for undated sprints and Kanban teams
The Dashboard’s Export Sprint CSV button failed with an error for a team whose recent sprints have no dates, and for a team with no sprints at all, such as a Kanban team. Sprints without dates are now left out of the export. A team with nothing to export sees “There is nothing to export yet…” with the step to set sprint dates in Boards → Iterations, in all six languages. A real failure now shows plain-English wording instead of an Azure DevOps error code. Teams whose sprints all have dates see no change. When the export or Cumulative Flow fails, the error report we receive now carries the technical error type and HTTP status code, as dashboard tiles already do. It never includes the error message or any of your work-item data.
6.58.1, 6 October: Cumulative Flow handles sprints with no dates
A sprint with no start or end date is the default in a brand-new Azure DevOps project. For some viewers, Cumulative Flow stopped with an error on such a sprint instead of loading. It now shows “Sprint 1 has no dates yet” (with your sprint’s name) and the two steps to set the dates in Azure DevOps. Cumulative Flow for sprints that have dates is unchanged.
6.58.1: Issues are counted on the default Basic process
In a new project on Azure DevOps’ default Basic process, WIP read 0, forecasts read “0 or more” and no completed items appeared. Basic’s backlog type is Issue, and Issue was missing from the built-in Planned Work list, so it was not counted until Item Types were saved. When nothing is saved and the project’s backlog is made of Issues, which is true for Basic and for any process inherited from it, Issue now counts as Planned Work, and the “These figures count…” note names it. Item Types you saved in Configuration are honoured exactly as before, and Agile, Scrum and CMMI projects are unchanged. Basic’s To Do, Doing and Done states were already classified correctly.
6.58.0, 5 October: generated pipelines handle unusual names safely
The extension generates pipeline files for the WIP monitor, delivery digest, Exec report digest, sprint alerts and performance precompute. They placed team, project and organisation names into the script as quoted PowerShell text, which no quoting scheme can make safe for every possible name. Names are now written in an encoded form that is decoded when the pipeline runs, so a name is only ever read as text. Names in the schedule display name and header comment are also neutralised for Azure Pipelines expression syntax, and a few invisible line-break characters are removed. Branch filters and the values the pipeline reads back are exactly as before.
- Pipelines you generated before this release keep their old text until you generate them again. Nothing breaks if you do not.
6.58.0: exports, Copilot setup guidance and smaller changes
Smaller changes in the same release.
- The configuration export no longer includes the Teams and Slack webhook URLs saved in WIP and sprint-alert team scopes, so a shared export does not carry them. Enter them again after an import.
- GitHub Copilot setup guidance, in all six languages, now recommends a read-only token (a classic token with read:org, or a fine-grained token with read-only Copilot permissions) instead of manage_billing:copilot, which can also add or remove paid seats. Tokens you have already saved are not changed. If yours has the broader scope, you can replace it with a read-only token.
- In Configuration → Scheduled Reports, you’ll now see recipient addresses on your subscriptions partly hidden (for example j•••@acme.com). Reports are still delivered to the full address.
- Help now checks a documentation link stored for your organisation each time it reads the link, not only when the link is saved.
- The hub’s browser security policy no longer allows connections to two AI service addresses that the extension stopped using in July.
6.58.0: the hub confirms which organisation it is running in
About once per session the hub confirms which Azure DevOps organisation it is running in. It uses the short-lived token Azure DevOps issues to the signed-in user, for that one check only, and it asks for no new Azure DevOps permission. Configuration, Privacy and Data & Privacy explain this in all six languages.
Related: Privacy policy
What you need to do
Nothing is required. Azure DevOps updates the extension automatically. To give pipelines you generated before 6.58.0 the new name handling, generate them again in the extension. 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. Work-item content stays in your Azure DevOps tenant.
Related: Service status