Release NotesMay 23, 2026· 4 min read

Agile Analytics 6.11.2 — Feature Analytics scope filter, Linked PRs in User Metrics

v6.11.2 ships two reporting fixes customers raised during evaluation and adds zero new Azure DevOps permissions. Feature Analytics now respects the team scope you save in Configuration → Feature Filters end-to-end — the feature list itself trims to scope, not just the per-team aggregate table and Completed-SP totals. User Metrics gains a new Linked PRs column that counts pull requests attached to each user's assigned work items, populated from work-item relations so the upgrade is silent — no admin re-authorisation prompt. PR comment counts remain unavailable in this build and now render as an em-dash instead of a misleading zero.

#release notes#6.11.2#feature analytics#user metrics#linked prs#scope#pull requests#azure devops

v6.11.2 is a focused patch release: two reporting fixes that customers raised during evaluation, with no new Azure DevOps permissions requested. Existing installed orgs auto-update silently from the Marketplace — no re-authorisation prompt, no admin action required, and every existing Configuration setting, license, scope, and dashboard preference is preserved byte-for-byte. The two changes are intentionally narrow so you can read and absorb them in a few minutes.

What's new

  • Feature Analytics now respects your saved team scope end-to-end. When you save a team scope in Configuration → Feature Filters, the feature list itself trims to that scope — not just the per-team aggregate table and Completed-SP totals. Previously the filter saved correctly and the team-by-team summary numbers honoured it, but the feature list still rendered every Feature in the project, which made scoped reports confusing.
  • New Linked PRs column in User Metrics. Counts pull requests attached to each user's assigned work items during the sprint range — a strong proxy for PR authorship that's accurate in the vast majority of teams. The column header tooltip explains the data source so anyone reading the report knows what they're looking at.
  • PR comment counts now render as an em-dash (—) instead of a misleading 0. The metric needs an Azure DevOps permission the extension does not request, so showing 0 was misleading. An em-dash is honest about what's available.

About the Feature Analytics scope fix

When you scope Feature Analytics to specific teams (Configuration → Feature Filters), the dashboard's per-team aggregate table, Completed-SP totals, and KPI strip all correctly trimmed to the saved teams. But the feature list — the per-feature rows below the KPI strip — kept rendering every Feature in the project, with non-scoped features just showing 0 stories and 0 SP. That created a mismatch: the totals at the top would say a scope had 2 teams and 146 story points while the list below showed 50 features from 7 teams. v6.11.2 closes that gap. The feature list now shows only features whose own area or iteration path belongs to a scoped team, or that have at least one child story in a scoped team — so the list count and the totals line up.

About the Linked PRs metric

The new Linked PRs column counts pull requests attached to each user's assigned work items in the selected sprint range. The data comes from Azure DevOps work-item relations (ArtifactLink with attribute name "Pull Request") and uses only the extension's existing read scopes — no new permission is required and no re-authorisation prompt fires on upgrade. The signal usually matches PR authorship one-to-one: the developer assigned a story typically opens the PR for it. It can drift by one in a few edge cases — pair programming where two developers share a story but only one opens the PR, mid-sprint reassignment that moves an existing PR-linked story to a new owner, or PR-on-behalf-of scenarios where a senior engineer opens a PR for a junior's story. The column header tooltip surfaces the data source so reviewers can interpret the number correctly.

Pricing reminder

Three per-seat plans, every feature included on each: Team — $25/month (2 seats), Business — $100/month (6 seats), Premium — $2,000/year (unlimited seats). The 30-day free trial activates automatically on install — no credit card required. If you're on the trial or comparing options, the pricing page has the full details, and you can schedule a 15-minute call (no slides) for procurement, security review, or sizing questions.

Updating

The extension auto-updates from the Marketplace, so existing customers don't need to do anything. There are no scope changes in this release, which means the upgrade is silent — no admin re-authorisation prompt and no consent screen. Every Configuration setting, license, and dashboard preference is preserved byte-for-byte. The first time you open the hub after the upgrade, the in-product changelog popup will show the v6.11.2 highlights once and then dismiss permanently. New installs can grab v6.11.2 from the Marketplace listing at https://marketplace.visualstudio.com/items?itemName=Baytek.agile-analytics.

Compare your Azure DevOps reporting options before you commit

See how built-in ADO reporting, Power BI, and Marketplace extensions stack up — then start the 30-day trial to evaluate the extension path inside your own organisation.

Related reading