v2.4.9 is a focused quality release. Package comparison against v2.4.8 shows only two changed files: extension.vsixmanifest (version bump) and dist/hub.js (runtime behavior update). The update targets Feature Analytics team scoping so reported rows align more reliably with selected scope in real customer projects.
What Changed in v2.4.9
- Feature Analytics team matching now resolves scoped teams using normalized tokens and preserved labels.
- Child work-item fetch now includes System.IterationPath in addition to Area Path, improving team-resolution fidelity.
- Team include/exclude filtering is now applied to resolved scope tokens, reducing false matches in large project structures.
- Package manifest version updated from 2.4.8 to 2.4.9.
Why This Matters for Data Correctness
- Feature rows are less likely to drift into the wrong team bucket when area paths are complex.
- Scope behavior is more consistent for organizations that rely on iteration naming or mixed path structures.
- Leaders reviewing cross-team metrics get cleaner attribution and fewer manual cross-checks.
Getting Started in Under 2 Minutes (Required Sequence)
Use this exact sequence during onboarding to avoid incorrect analytics behavior:
- Step 1 — Install: Open the Marketplace listing, review the plan that fits your organization, then install the extension into your Azure DevOps organization.
- Step 2 — Open: Navigate to any project and open Agile Analytics from the left hub navigation (under your project name).
- Step 3 — Claim Admin Access (Required): An Azure DevOps Project Administrator or Organization Administrator must go to Tools → Configuration → Access Control and click Claim Admin Access.
- Step 4 — Configure Workflow Mapping (Required): Go to Tools → Configuration → Workflow Mapping, map your Azure DevOps board states to analytics flow stages based on your company process, and save.
- Step 5 — Select your team and explore: Use the team selector in the top-left corner, then browse views using the top navigation.
- Starter lets each user work with one selected team in one project at a time while still browsing all projects and teams from the toolbar.
- Pro expands to up to 3 teams in 1 project and adds Team Leaderboard.
- Business expands to 10 teams across 3 projects and unlocks Access Control plus custom workflow mappings.
Optional Additional Setup
- After required setup is complete, go to Tools → Configuration to set WIP limits.
- Add Teams/Slack webhook alerts.
- Run Readiness checks.
- Export Support Diagnostics.
Rollout Guardrail
For correct analytics behavior in customer environments, complete Access Control claim and Workflow Mapping before broad team rollout.