Why this release exists
A handful of customers told us the same thing in different words over the last six weeks: “auto-discovery doesn’t understand our team’s workflow.” Sometimes that was a language gap. Sometimes it was a custom state (“Awaiting Validation”, “GxP Approved”, “Deployed”, “UAT”) that English-only auto-discovery just didn’t know. Either way, the symptom was the same — Cycle Time and Flow Efficiency rendering against an incomplete mapping, with no in-product hint that anything was wrong. 6.14 fixes both the silence and the language gap.
Auto-discovery now speaks six languages
Italian, German, and French join English, Spanish, and Portuguese. We added roughly 225 new keywords across all six, covering the workflow-stage names teams actually use in the wild — Implementing, UAT, Awaiting Review, Deployed, Accepted, Acceptance Review, En revisión, Em homologação, In collaudo, In Prüfung, En cours d’exécution, and a long list of equivalents. If your team’s state names follow any reasonable pattern in those languages, auto-discovery should classify them on day one.
You’ll see it the moment something’s off
When auto-discovery can’t bucket one of your states, you now get a clear banner on Dashboard, Cycle Time, Flow Efficiency, Live Stats, and Sprint Summary — the views that actually depend on the mapping being right. There’s also a quiet count badge on the Workflow Mapping nav, and a one-shot welcome toast for fresh installs whose discovery left something unclassified. Open the tab, fix the gap, and every signal disappears.
Workflow Mapping now learns from you
Drag a previously-unrecognised state into a bucket on the Workflow Mapping tab and save — that’s it. Future auto-discovery on this organisation will respect that choice, across projects, and on state names that follow the same convention. A small “team-learned” badge sits next to each entry you taught us so you can tell at a glance which keywords came from your team versus our defaults. There’s a Clear button if you ever want to start over.
Already installed before 6.14? You’ll see a one-time re-discovery prompt
If you’ve been running Agile Analytics for a while and your saved Workflow Mapping still has unmatched states, the next hub load shows a one-time prompt: “Auto-discovery now recognises more languages and workflow names. Want to re-run on this organisation? We won’t change anything until you confirm.” It shows a diff preview — the exact list of state names and which bucket each one would land in — before saving anything. Buckets you’ve already classified by hand are never touched.
What’s also been tidied up
The “what’s new” pop-up that appears on first hub load after an upgrade has been slimmed down: the inline pricing block is gone, the release recap is trimmed to the last three versions, and there’s a permanent View pricing button in the footer if you ever want to check the tiers. Pricing details belong on the pricing page, not in your way every release.
Updating
Auto-update from the Marketplace; no admin action required. No new ADO scopes, no re-authorisation prompt, no consent screen. Every Configuration setting, license, mapping, and dashboard preference is preserved exactly. New installs: grab v6.14.0 from the Marketplace listing at https://marketplace.visualstudio.com/items?itemName=Baytek.agile-analytics.