More accurate Planned Items in Sprint Summary
A work item counts under Planned Items when its own Azure DevOps history shows it was already in the sprint at the end of day 1, for example a story planned the day before the sprint starts. It is then no longer listed under "added to the sprint after Day 1". Scope Change and commitment reliability follow the same rule in every view and in the local AI connector. Work items with a very long history (more than 200 changes) now always have their most recent sprint moves and state changes read, so sprint figures and cycle time use the whole history.
Clearer wording on the Data & Privacy page
The Data & Privacy page now lists pipelines among the data read from Azure DevOps. From pipelines, the extension reads the pipeline names and run history for DORA metrics and, if an admin turns on "Measure lead time from linked deployments", the work items linked to each run. The Access Control list can be read by people in your organisation who have access to the extension. Configuration, Privacy describes the administrator sign-in name more precisely: it is recorded once per organisation the first time they open the hub, and you can ask us to delete it at any time.
More ways to find a view
Find a feature in the Ask AI panel understands more ways to search: say/do (commitment reliability) now also finds Sprint Summary, and "saydo", "road map" and "time line" work too, with local words in Spanish, Portuguese, Italian, German and French. On the Marketplace, Agile Analytics is easier to find when you search for Epic, roadmap, timeline or portfolio, and the listing opens with the Epic Timeline.
What you need to do
Nothing; Azure DevOps updates the extension automatically. Local AI connector users on @latest get 6.79.2 automatically.
Related: 6.79.1: Use your own AI assistant · Full release history