Keep HaloITSM and Azure DevOps perfectly in sync
Give dev and ops one shared record. ZigiOps syncs HaloITSM Tickets with Azure DevOps Work Items in real time — no scripts required.
HaloITSM 
Azure DevOps Dev teams track work in Azure DevOps, but the service desk runs on HaloITSM. A bug tied to an open ticket means someone manually keeps both records current by hand.
ZigiOps links HaloITSM Tickets to Azure DevOps Work Items in both directions, so status, priority and comments stay in sync — dev and ops work from the same up-to-date record.
How the HaloITSM ↔ Azure DevOps mapping works inside ZigiOps
A look at the visual field-mapping canvas ZigiOps engineers use to configure this pair — point, click, connect. No scripts, no pipelines.
HaloITSM 
Azure DevOps Per field, not per record — if only the priority changed on one side, only that field is resolved, not the whole ticket.
Lock specific fields (e.g. Priority) to always defer to one system, regardless of which side changed last.
Route simultaneous conflicting edits to a review queue instead of silently picking a winner, when that's the safer default.
HaloITSM connector Azure DevOps connector HaloITSM ↔ Azure DevOps FAQ
Can a HaloITSM ticket automatically create a work item in Azure DevOps?
Yes — and the reverse holds too. When a developer updates the work item, the linked HaloITSM ticket reflects it automatically.
Does this work with both Agile and Scrum work item types in Azure DevOps?
Yes — ZigiOps maps to whatever work item type (Bug, Task, User Story, etc.) your project template uses; that mapping is configured during setup, not hardcoded to one process.
Is this a one-way trigger or true two-way sync?
True two-way. Comments, status and priority all sync bidirectionally — unlike lighter automation tools that only push data in one direction.
See HaloITSM ↔ Azure DevOps sync live
Book a demo and we'll connect your HaloITSM and Azure DevOps instances in real time.