Konductro.

Azure DevOps

Konductro integrates with Azure DevOps for organisations that use ADO as their git provider and work item tracker. ADO acts as a kanban mirror — Konductro owns the workflow, ADO provides visibility and auditability.

What Syncs

DataDirectionDetail
TicketsKonductro to ADOStories pushed as User Stories. No Tasks, no iteration paths — ADO mirrors the Konductro board state
StatusKonductro to ADOTicket status changes in Konductro are reflected in ADO work item state
BranchesKonductro to ADOFeature branches created via ADO Git API when a developer starts work
Pull requestsKonductro to ADOPRs created with title, description, and acceptance criteria checklist
ReviewersKonductro to ADOAssigned reviewer added to the PR on ADO
Ticket specsKonductro to ADO.tickets/TICKET-KEY.md files pushed to the repo via ADO Git push API

How It Works

Konductro uses the Azure DevOps REST API with a Personal Access Token (PAT) for authentication. The PAT requires the following scopes:

  • Work Items — Read & Write (for ticket sync)
  • Code — Read & Write (for branch creation, PR creation, file push)
  • Graph — Read (for user identity resolution)

Setup

1

Generate a PAT in Azure DevOps

In ADO, navigate to User Settings and then Personal Access Tokens. Create a token with the scopes listed above. Set an appropriate expiration.

2

Configure in Konductro

In Konductro, go to the project's Settings and then Integrations. Enter the ADO organisation name, project name, and PAT.

3

Link repositories

Add repositories from your ADO project. Konductro discovers available repos and lets you link them to the project.

ADO as a Kanban Mirror

ADO is not a parallel workflow — it is a read-through view. Teams that need ADO for compliance, reporting, or client visibility get it without maintaining two systems. All actions (start work, create PR, transition to QA) happen in Konductro and are reflected in ADO automatically.

This means:

  • No duplicate data entry
  • No drift between what Konductro says and what ADO shows
  • Stakeholders who live in ADO see accurate, real-time status