Version 3.7.2 is a meaningful upgrade for teams whose Azure DevOps process template does not use the standard Scrum type names. It also ships Sprint Summary dark mode support and two fixes for the commitment-lock scope change tile. Here is what changed.
Item Type Category Mapping — Support Any ADO Process Template
Agile Analytics previously assumed your work item types were named User Story, Story, Bug, and Research. If your organisation uses Scrum (User Story), Agile (User Story), CMMI (Requirement), SAFe (Feature, Enabler), or any custom process — your items were being excluded from sprint metrics silently. Version 3.7.2 replaces every hardcoded type reference with a fully configurable mapping.
- A new "Item Types" tab in the Configuration panel lets you map your ADO type names to three abstract analytics categories: Story-equivalent, Bug-equivalent, and Research-equivalent.
- Auto-detect from ADO reads your project's process template via the ADO API and suggests the right type names automatically — works with Scrum, Agile, CMMI, SAFe, and every custom process.
- The mapping is org-scoped per project — configured once by an admin, applied for all users.
- Sprint Summary, Cycle Time Scatterplot, Live Stats, Sprint Burndown, and the Workflow Tab type selector all use the mapping — no more hardcoded type names anywhere.
- Legacy metric_work_item_types config is kept as a fallback for existing installations.
Sprint Summary — Full Dark Mode
All Sprint Summary cards now respond correctly to the Azure DevOps dark theme. Previous versions applied no dark mode styles to the sprint cards, so the entire Sprint Summary view appeared light even inside a dark-themed ADO instance.
- Toolbar, sprint selector, date chips, and dropdown now use dark surface colours.
- All five metric tile tones (neutral, positive, warning, negative, info) have dark variants.
- Breakdown cards, rule pills, math explainer, team card shell, and header all themed.
- Loading, error, and empty states updated with dark-safe colours and spinner.
- Removed items panel and carryover badges dark-themed to match.
Commitment Lock Accuracy — Two Fixes
The Sprint Summary commitment lock (end of Day 2) had two display bugs that have been corrected.
- Pre-cutoff scope change false positive: adding an item on Day 1 was showing +1 in the Scope Change tile before the lock was reached. The tile now shows "—" with a "Commitment lock not yet reached" message until Day 2 ends.
- Pre-cutoff removal false positive: items removed before Day 2 were appearing in the "removed after commitment lock" panel because a fallback timestamp of today was being used when no removal time was recorded. The panel now only shows items with a confirmed post-cutoff removal timestamp.
- Updated wording from "removed mid-sprint" to "removed from sprint scope after Day 2" for clarity.
Update to 3.7.2 from the VS Marketplace to get all of these improvements.