← All integrations

GroundTruth keeps your Azure DevOps Boards accurate to your code. It reads your work items, links each to the branches and pull requests that implement it, and writes the correct state back, only when the work and the acceptance criteria agree.

What we read

• Work items in a project via a WIQL query, then a batch expand of the fields we need.
• System.State, work-item type, assignee, changed date, and the parent link for hierarchy.
• The description and the Microsoft.VSTS.Common.AcceptanceCriteria field, with HTML flattened to plain text.

Azure DevOps work items are numbered rather than keyed like PROJ-123. GroundTruth uses the numeric work-item id (for example 1042) as the ticket identifier throughout.

What we write back

Azure DevOps has no separate transition objects; a status change is a field update. GroundTruth sends a JSON-Patch that sets System.State to the correct value for the target category, using the application/json-patch+json content type your Boards process expects. Every write is recorded in the audit chain with the prior state and is revertible.

Acceptance-criteria gate

A completed pull request will not push a work item to Done while its acceptance criteria are unmet. It is set to Resolved (review) and flagged for a human instead.

Setup

1. Connect with a Personal Access Token (used as Basic auth with a blank user), or via Azure AD OAuth.
2. The endpoint is your organisation URL, for example https://dev.azure.com/your-org; set the project to sync.
3. We backfill open work items, then keep them current from service hooks.

Continuous sync

Add Azure DevOps service hooks for the work item created and updated events, pointed at the URL we give you on connect. GroundTruth reconciles each change as it arrives.

State mapping

States vary by process (Agile, Scrum, Basic, or a custom template). We map the standard states above and let you override the target state name per workflow.