Workflow mapping tells Agile Analytics which of your ADO board columns correspond to "in active work" and "done" — the anchor points used for cycle time, lead time, and throughput calculations. Getting this mapping right is a one-time task, but the setup checklist used to ask for it on a per-project basis.
The Old Behaviour
When an admin switched to a project that had never loaded the Agile Analytics hub, the checklist would flag "Required: Configure Workflow Mapping" — even if the admin had already saved a mapping for another project in the same organisation. This created unnecessary noise and made it look like something was broken.
What Changed in 3.6.0
The workflow-mapping checklist step is now evaluated at the organisation level, not the project level.
- If a workflow mapping exists for any project in the organisation, the checklist step shows as complete across all projects.
- Admins who have already configured mapping in one project will not see the step flagged when switching to another project.
- New organisations that have not yet saved any mapping will still see the prompt correctly.
One Setup, Every Project
This change reflects a broader design principle: administrative configuration that applies organisation-wide shouldn't require repeated per-project acknowledgement. Workflow mapping, once established, travels with you as you move between projects. Combined with the setup-banner fix also shipping in 3.6.0, admins can now switch between projects freely without the product appearing to forget who they are.
Update to Agile Analytics 3.6.0 from the VS Marketplace to get this and all other 3.6.0 improvements.