Agile Analytics 3.1.5 — Our Biggest Release Yet

Version 3.1.5 is the biggest release since Agile Analytics launched. Three dashboard widgets bring sprint health data directly to your Azure DevOps homepage. Four new analytics views — Cumulative Flow, Multi-Team Aging, Audit Trail, and Data & Privacy — fill the remaining gaps in sprint visibility. Navigation is reorganised into five clear groups, and every metric now runs through your saved workflow mapping. 211 automated tests are passing across 20 test files.

Dashboard Widgets

You can now pin Agile Analytics data directly to your Azure DevOps dashboard without opening the hub. Three widgets are available.

New: Cumulative Flow Diagram

The Flow Analytics group now includes a Cumulative Flow Diagram (CFD) — a stacked area chart showing how work items move through six workflow stages (New → Queued → In Progress → Test → Review → Done) over time. The chart is built from your work item state events, replaying each item's state history day by day through your configured workflow mapping. If your team uses custom state names, the mapping you saved in Configuration → Workflow Mapping determines which stage each state falls into.

New: Multi-Team Aging

A dedicated view under the Agile Coach group that shows aging work-in-progress across multiple teams at once, so coaches and managers can spot blocked items without switching context.

New: Audit Trail

The Audit Trail view (under Tools) shows a per-sprint, per-work-item timeline of every state transition.

• Each work item with its type colour-coded (Story blue, Bug red, Research purple, Feature amber, Task slate)
• Timestamps for every state change
• Duration between transitions
• Expand/collapse per item for full event detail
• Useful for sprint reviews and retrospectives where you need to understand exactly when and how items moved through the workflow

New: Data & Privacy

An in-app transparency page (under Tools) that documents exactly what the extension accesses and stores.

• 5 trust badges: No external data transmission · No backend server · Read-only ADO access · Settings stored in ADO only · No third-party analytics
• ADO permissions: vso.work (read-only), vso.project (read-only), vso.graph (read-only) — no write permissions requested
• Data inventory: work items (title, type, state, area, iteration, points, dates), state history, sprints/iterations, teams, projects
• Point procurement reviewers to this tab instead of preparing a separate document

Navigation Reorganised

The sidebar now groups 20 views into five themed sections: Sprint Health (Dashboard, Live Stats, Multi-Team Scope, Delivery Signals, Sprint Summary), Flow Analytics (WIP Monitor, Flow Metrics, Cumulative Flow, Aging & Blocked, Cycle Time, Monte Carlo), Portfolio (Team Leaderboard, Feature Analytics), Agile Coach (Agile Report, Multi-Team Aging, User Metrics), and Tools (Retro Snapshot, Audit Trail, Data & Privacy, Configuration).

Sprint Summary

Sprint Summary gives teams a single-screen snapshot of each sprint.

• Committed set locked at end of day 2 — the first two days cover planning refinement and late additions from distributed teams
• Scope change shown as net additions and net removals — bounces (out-and-back-in) are neutral
• Carryover based on workflow state position, not estimate fields
• Removed Items Panel listing each removed item by title, type, and state at removal
• Multi-team comparison with independent sprint selectors and CSV export
• All data is derived from System.IterationPath revision history via the EVER WIQL keyword — not from current board state

Workflow Mapping Drives Every Metric

Carryover, completed counts, cycle time start/end points, scope change, CFD stage assignment, and health score inputs all now read from your saved workflow mapping. If your team uses custom state names, the mapping you configured in Configuration → Workflow Mapping determines what counts as Done, In Progress, or Committed across every view. If you have not mapped your workflow yet, doing so takes about two minutes and immediately improves every metric in the extension.

Performance Precompute Pipeline

A new utility in Configuration can generate a YAML Azure Pipeline definition that runs nightly at 02:00 UTC, checks the current iteration for each scoped team, and produces a JSON snapshot artifact. This pre-caches data so hub views avoid heavy fan-out queries on page load.

Bug Fixes

Several stability and correctness issues have been resolved in this release.

• Race condition on rapid project switch — stale team lists from cancelled requests no longer render
• Dev tier switcher now writes to the same localStorage key that TierContext reads
• Notification trigger no longer fires with a blank team name on first load
• Extension data manager deduplicated — user-scoped and org-scoped storage share one factory
• Session caches now purge expired entries on each write instead of accumulating forever
• ADO user search capped at 100 results to match the Graph API default page size
• Setup banner can now be dismissed and stays dismissed across page reloads

Security & Accessibility

Accessibility and security improvements ship with this release.

• AI API key browser visibility warning on the AI settings form
• Nav tabs follow the ARIA tab pattern (role="tab", aria-selected, descriptive aria-label)
• Theme toggle has accessible labels
• Lock icon on tier-gated tabs marked aria-hidden="true" with a text label for screen readers

Test Coverage

211 automated tests across 20 test files, up from 179/13 in v2.5.4. Key additions include Sprint Summary scope logic (6 tests covering baseline removals, bounces, mid-sprint additions, carryover, and done-state removals), tier resolution and tier gate coverage, race condition, setup banner dismiss, ARIA tab, empty sprint, and no-dates-fallback tests, AgingChart and SprintSummaryView test suites, plus API contract and smoke tests that gate every build.