Lead time, measured to the deploy that shipped it
Until now, lead time for changes was a work-item proxy: activation to close, labelled as such. Useful — but "closed" and "deployed" are not the same moment. 6.33 adds a second measurement that uses the work items Azure DevOps already links to every pipeline run (AB# commit mentions and linked pull requests): for each completed item, lead time to the successful run that actually shipped it. It is opt-in under Configuration → DORA Metrics, appears beside the work-item measure, and never replaces it. Everything runs in your tenant with the read-only scopes you already granted — no new permissions, no data leaving Azure DevOps.
Honest by construction
This measurement is only as good as your linking discipline, so the card says exactly what it is standing on: "N of M completed items had a linked deploy · newest B of T successful runs sampled," with a weekly trend. Teams that rarely mention work items in commits will see low coverage — not confident numbers built on thin air. And because a green pipeline run is not always a deployment, a picker lets you choose which pipelines count (default: all), so a busy CI pipeline can't masquerade as daily deploys.
Know when your installed version has fallen behind
Azure DevOps usually updates extensions when you reopen them — but "usually" has exceptions, and some organisations quietly fall several versions behind without anyone noticing. When the version you are running is two or more releases behind the Marketplace, a slim dismissable notice now says so, including the fix when reopening isn't enough: an organisation admin may need to approve the update under Organization settings → Extensions.
Sharper paths and clearer words
The Dashboard now links straight to Next Sprint Planning beside Sprint Velocity — the view that answers "what should we commit to next sprint?" was too easy to miss. The SLE Violations page orders targets worst-first, counts violations in a summary strip, collapses an all-quiet board into one guided panel, and widens to 3, 6, or 12 sprints. Every "No data" SLE row explains in plain words what that target counts and where to adjust it. A DORA "Low" badge now states which cutoff was crossed and what the next level takes — a measurement, not a verdict. And field pickers across Configuration list your organisation's own fields first, ADO built-ins below.
Fixed: the refresh that forgot your team
A browser refresh — especially a hard refresh — could restore your project but come back with no team selected, leaving views empty until you picked it again. The saved team now restores reliably, with a sensible fallback when it no longer exists. And 6.33.1, shipped the same day, tidies the SLE Violations table: cycle times now show clean one-decimal numbers instead of an occasional full floating-point tail.
Updating
The update applies automatically when you reopen the extension — nothing to install. The What's New popup shows the highlights once. The deploy-linked measurement stays off until an admin enables it, so nothing changes on your DORA view until you decide it should. Questions about what the new measurement is telling you? Ask Henry from the top bar — we reply personally within 24 hours.