Version 2.3.2 focuses on operational confidence: before you roll out Agile Analytics to a new team, you should know which dashboards will work straight away and which need a little configuration first. And when something unexpected happens, your support log should already be captured inside your own tenant, ready to share in seconds. Two new Configuration tabs — Customer Readiness and Support Diagnostics — deliver exactly that.
Customer Readiness Tab
The Customer Readiness tab runs a live pre-flight check against your Azure DevOps project and team data. It validates workflow state mappings, sprint history, work item availability, and team configuration — then gives each analytics dashboard one of three statuses:
- Ready — all required data is present; the dashboard will load immediately
- Limited — data exists but some checks have gaps (e.g. fewer than 4 past sprints for trend analysis)
- Blocked — a critical dependency is missing (e.g. no workflow state mapped to "Done")
Why It Matters
Without the readiness check, a new user opening Cycle Time or Flow Efficiency on a freshly installed org would see an empty chart with no clear explanation. The readiness tab surfaces the root cause before that confusion happens:
- See which dashboards are immediately usable and which need setup steps
- Get specific "Next step" guidance per failed check — e.g. "Map a workflow state to Done in Configuration → Workflow Mapping"
- Run on-demand for any team in the project from the team selector dropdown
- No external tools or scripts required — the check runs entirely inside ADO using saved configuration and live API data
Support Diagnostics Tab
The Support Diagnostics tab is a sanitized error log stored inside your Azure DevOps Extension Data Service. Every time the extension encounters an unexpected error — a failed API call, a render failure, an unhandled exception — it writes a structured event to this log with contextual metadata: the view, project, team, and operation that triggered it.
What Is Captured
Each log event includes a severity level (error, warn, info), a short code identifying the failure type (e.g. dashboard_snapshot_load_failed, live_stats_load_failed, view_render_failure), a human-readable message, and the context — which view, project, team, and operation was active. Work item titles, user names, and other personal data are never included.
Exporting the Bundle
When you need help diagnosing a problem, click "Copy Diagnostics" or "Download JSON" to export the full bundle. The copy button handles Azure DevOps's iframe clipboard restrictions with an automatic fallback — if the clipboard API is blocked, the JSON is auto-selected in a textarea so you can Ctrl+C it manually. Once shared, you can clear the log with one click.
Error Telemetry — Wired Into Key Views
In v2.3.2 the diagnostic capture is wired into four surfaces so errors are recorded automatically without any user action:
- Dashboard — snapshot load failures and export failures are logged with operation context
- Live Stats — load failures and unhandled exceptions captured separately for easier triage
- View Error Boundary — any render-level crash in any view is caught and logged with the view, project, and team IDs
- Hub root — the capture layer is installed on mount so logging starts the moment the extension loads
LiveStats Scoping Fix
v2.3.2 also fixes a bug in the Multi-Team Scope view where teams already added to the scoped list would still appear in the "Add team" dropdown. The available source teams are now filtered to exclude teams already scoped, and the dropdown shows "All teams already scoped" when the list is empty. The "Add All" button is also disabled in that state to prevent duplicate entries.
Settings Persistence (v2.3.0 Foundation)
These diagnostics features build on the settings persistence fix shipped in v2.3.0: all configuration — WIP limits, workflow mappings, notification webhooks, AI settings, access control, and user preferences — is now stored using the Azure DevOps Extension Data Service key-value API. This means upgrading the extension will never reset your configuration, and the readiness checks read the same saved config that your dashboards use.