Docs / Connecting Azure DevOps
Connecting Azure DevOps
Personal access token, work item queries, and what write-back can and can’t change.
Set up
- In Azure DevOps: User settings → Personal access tokens → New Token.
- Scope it to Work Items → Read & Write. Read-only works for syncing, but write-back will fail without Write.
- In Z3NTRA: Systems → Connect a system → Azure DevOps.
- Organization — the
dev.azure.com/<organization>segment. - Project — optional; leave blank to search the whole organization.
- Personal Access Token — the token from step 2.
- Organization — the
What gets pulled in
Work items assigned to you, queried with a default WIQL that excludes removed items and orders by most-recently-changed. Status is read from each work item type's own state categories (Proposed / In Progress / Resolved / Completed / Removed) rather than matching on state names — so a custom process template still lands in the right bucket without any configuration. Blocked has no category of its own and is handled separately.
What write-back changes
Edits go through as a JSON Patch against the work item, with the item's revision checked immediately beforehand so two edits can't silently clobber each other.
One field isn't always availableNot every work item type exposes a due date (the Basic process template, in particular). If yours doesn't, Z3NTRA retries the write without it and shows a warning rather than failing the whole edit.