Azure DevOps Cherwell integration: two-way sync without scripts
Keep Azure DevOps and Cherwell perfectly in sync
Give engineering and the service desk one shared record. ZigiOps syncs Azure DevOps Work items with Cherwell Incidents in real time — no scripts required.
Azure DevOps 
Cherwell Engineering tracks work in Azure DevOps, but the service desk runs on Cherwell. When an Incident needs a code fix, or a Work item needs to reach the person who filed it, someone re-types it into the other system by hand.
ZigiOps links Azure DevOps Work items to Cherwell Incidents in both directions, so status, priority and comments stay in sync — engineering and the service desk work from the same up-to-date record.
How the Azure DevOps ↔ Cherwell 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.
Azure DevOps 
Cherwell 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.
Azure DevOps connector Cherwell connector See the Incident-to-Resolution solution → See Azure DevOps ↔ Cherwell sync live
Book a demo and we'll connect your Azure DevOps and Cherwell instances in real time.