Zammad Azure DevOps integration: two-way sync without scripts
Without integration, support re-creates every Zammad ticket as an Azure DevOps work item and chases engineering for status.
Zammad 
Azure DevOps Support receives the bug report in Zammad, but the fix is tracked in Azure DevOps. Without a connection, someone re-creates the ticket as a work item, and the outcome has to be relayed back to the customer record by hand.
ZigiOps creates an Azure DevOps work item for each Zammad ticket you select and links the two with correlation fields. Changes and files on the work item are written back to the Zammad ticket automatically.
What manual work disappears
- Re-creating each Zammad ticket as an Azure DevOps work item
- Chasing engineering for status
- Copying comments and files between the two tools
- Translating states and assignees by hand
- Updating the ticket when the work item is completed
What does this handoff cost you?
A quick estimate for this integration.
Illustrative estimate based on your inputs. Not a guaranteed cash saving. Actual results depend on workflow design and volume.
How the Zammad ↔ 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.
Zammad 
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.
Zammad connector Azure DevOps connector See the Incident-to-Resolution solution → Every field that matters, mapped both ways
Map Zammad entities to Azure DevOps entities down to the individual field, without writing a script.
More control over how Zammad ↔ Azure DevOps syncs
Set how often ZigiOps checks for new and updated records, or trigger an action by hand with Run.
Pick up only what you need — for example tickets created or updated since the last run, or tickets matching a field value.
Each Zammad ticket is linked to its Azure DevOps work item through correlation fields, so ZigiOps always knows which record belongs to which.
Map ticket fields to Azure DevOps fields, including custom fields, by choosing them from a list — no code.
File content and file name are mapped, so files added on one side appear on the other automatically.
The Troubleshooting view shows every run, its result and how long it took, so failures are easy to spot.
A customer bug, fixed by engineering
Support logs a bug in Zammad while engineering tracks the fix in Azure DevOps. ZigiOps keeps both records on one shared thread.
Support creates a ticket describing the customer’s problem.
A matching Azure DevOps work item is created and linked to the ticket through correlation fields.
State changes, comments and attachments on the work item sync back to the ticket.
When the work item is completed, the Zammad ticket reflects it without anyone updating it by hand.
Zammad ↔ Azure DevOps FAQ
Is the Zammad–Azure DevOps sync two-way?
Yes. A Zammad ticket creates a Azure DevOps work item, and updates and attachments made in Azure DevOps are written back to the matching Zammad ticket. Correlation fields link each pair of records.
What fields map between Zammad and Azure DevOps?
Ticket ↔ work item, title ↔ title, state ↔ state, articles ↔ comments, and attachments ↔ attachments. Mappings are configured point and click in the field map, and you can add any field, including custom fields.
Do I need to write scripts or install plugins?
No. The integration is configured visually in ZigiOps. You connect Zammad with its URL and an API token, connect Azure DevOps, and build the workflow.
How does ZigiOps know which tickets to pick up?
The source side polls on an interval you choose, and a filter selects the records to sync — for example only tickets created since the last run. You can also run an action manually.
Can I see what happened on each run?
Yes. The Troubleshooting view lists every execution with its result and duration, so you can confirm each sync completed.
Show us your Zammad–Azure DevOps process.
Book a demo and we'll connect your Zammad helpdesk and Azure DevOps instance.