ServiceNow Jira integration: two-way sync without scripts
Without integration, teams copy the same incident twice and chase each other for status.
ZigiOps keeps ServiceNow incidents, problems, change requests and CMDB data in two-way sync with Jira, as often as every 10 seconds, without scripts, business rules or update sets. It is a standalone platform: nothing is installed inside ServiceNow, it runs as a ZigiWave-hosted cloud or on your own infrastructure, and it does not permanently store your data. Ready-made templates speed up setup, and a safe test mode checks everything before go-live. Licensed per workflow, from €500 a month, billed yearly.
ServiceNow 
Jira Support logs an incident in ServiceNow, engineering tracks the fix in Jira, and the two drift apart. Status updates and comments live in one tool and never reach the other, so teams reconcile by hand and customers wait.
ZigiOps links each ServiceNow incident to its Jira issue and keeps them synchronized in real time. Status transitions, priority, comments and attachments propagate both ways automatically — no scripts, no manual updates.
What manual work disappears
- Entering the same incident twice, once in ServiceNow and once in Jira
- Chasing engineering for status
- Copying comments and attachments between the two tools
- Translating states and priorities by hand
- Updating the incident when engineering closes the issue
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.
COCC
COCC uses ServiceNow for customer requests and Jira for DevOps projects, and connected the two with ZigiOps.
- Changes in ServiceNow update Jira automatically, and the other way round, in real time.
How the ServiceNow ↔ Jira 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.
ServiceNow 
Jira 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.
ServiceNow connector Jira connector See the Incident-to-Resolution solution → Every field that matters, mapped both ways
Map ServiceNow entities to Jira entities down to the individual field, without writing a script.
Before you book: what you need to know
| Question | Answer |
|---|---|
| Supported versions | Jira Software and Jira Service Management 7.x or newer, on Cloud, Data Center and Server. ServiceNow releases Utah, Vancouver, Washington DC, Xanadu, Yokohama, Zurich and Australia. For older releases, contact us. See the ServiceNow connector docs. |
| What syncs | Incidents, problems, change requests, requests and tickets, CMDB data and custom fields. ZigiOps reads the ServiceNow schema dynamically, so any field can be mapped, and templates are available for the most common entities. |
| Installation | Nothing is installed inside ServiceNow. ZigiOps is a standalone platform that connects through the API. |
| Access needed | A dedicated integration user in each system. In ServiceNow it needs read, create and write access to the entity being synced. Jira Cloud connects with OAuth 2.0: you sign in with your Atlassian account and approve the ZigiWave app, so no API token is needed. Jira Data Center and Server connect with Basic authentication. See the Jira connector docs. |
| Setup time | With ready-made templates, an integration can be built in about 10 minutes. |
| Sync speed | Continuous sync on an interval you configure, as short as 10 seconds. |
| Where it runs | ZigiWave-hosted cloud, or your own infrastructure. |
| Your data | ZigiOps does not permanently store the data it transfers. ZigiWave is ISO 27001 certified. See Security and compliance. |
| Price | Per workflow, from €500 a month, billed yearly. Cost does not rise with ticket volume. Cloud hosting, implementation and a free proof of concept are included. See pricing. |
| Try it | Start a free trial and connect your own ServiceNow instance, including a developer instance. A safe test mode validates mappings on real data before go-live. |
| Next step | Start a free trial · Book a demo |
More control over how ServiceNow ↔ Jira syncs
Changes in either system reach the other within the interval you set, as short as 10 seconds.
Scope every sync with filters on priority, project, assignment group or any custom field.
Built-in logic decides which update wins and logs every decision for full traceability.
Sync resumes on its own after downtime or network interruptions — nothing to restart by hand.
Validate field mappings and rules against real data before the integration goes live.
See sync status and catch failures early, without digging through logs.
When a sync fails, ZigiOps surfaces the likely cause and a suggested fix — no log-diving required.
Scripts are not the only way to get control. In ZigiOps you decide per field what syncs, which system wins and what is flagged for review, and you can test the result on real data before go-live. For a side-by-side with script-based tools, see ZigiOps vs Exalate.
A P1 incident, handled by both teams at once
When a major incident hits, the service desk and engineering work the same problem in different tools. Here's how ZigiOps keeps them on one shared thread.
The service desk opens a P1 incident with priority, description and affected CI.
A matching Jira issue appears instantly, mapped field-for-field, and linked to the incident.
Status changes, comments and attachments sync back to the incident in real time.
When engineering resolves the issue, the incident closes automatically with a full audit trail.
ServiceNow ↔ Jira FAQ
Is the ServiceNow–Jira sync two-way?
Yes. Incidents and issues stay aligned in both directions in real time, with conflict-resolution logic keeping both systems authoritative so neither overwrites the other.
What fields map between the two?
Incident ↔ issue, status ↔ state, priority, and comments and attachments — all in both directions with full fidelity. Mappings are fully configurable in the visual editor.
Do I need to script anything in ServiceNow or Jira?
No. The entire integration is configured no-code in ZigiOps — no business rules, update sets or Jira automation to build or maintain.
Can I connect multiple ServiceNow or Jira instances?
Yes. ZigiOps supports unlimited connections between instances, so one Jira project can sync with several ServiceNow environments — or the reverse — each with its own field mapping and rules.
What happens if an incident and issue are updated at the same time?
Built-in conflict-resolution logic decides which update takes precedence and logs the decision, so both systems stay authoritative and every change is auditable.
Can I limit the sync to specific incidents or issues?
Yes. Conditional triggers let you scope the sync by priority, assignment group, project or any other field, so only the records that matter cross over.
Which ServiceNow–Jira integration tool should I choose?
It depends on your existing stack and compliance needs — see our how to choose a Jira–ServiceNow integration tool guide. If you're specifically consolidating incident response across ITSM and DevOps/monitoring tools, also see our incident management solution page.
Which ServiceNow and Jira versions does ZigiOps support?
ZigiOps supports Jira Software and Jira Service Management 7.x or newer, on Cloud, Data Center and Server. For ServiceNow it supports the Utah, Vancouver, Washington DC, Xanadu, Yokohama, Zurich and Australia releases; contact us for older releases. See the connector documentation for details.
Do I need to install anything in ServiceNow?
No. ZigiOps is a standalone platform that connects through the ServiceNow API with an integration user, so nothing is installed inside ServiceNow.
What access does the integration need?
A dedicated integration user in each system. In ServiceNow it needs read, create and write access to the entity being synced. Jira Cloud connects with OAuth 2.0: you sign in with your Atlassian account and approve the ZigiWave app, so no API token is needed. Jira Data Center and Server connect with Basic authentication.
Where does ZigiOps run, and does it store my data?
It runs as a ZigiWave-hosted cloud service or on your own infrastructure. It does not permanently store the data it transfers, and ZigiWave is ISO 27001 certified.
Can ZigiOps sync CMDB data and custom fields?
Yes. ZigiOps reads the ServiceNow schema dynamically, so incidents, problems, change requests, requests, CMDB data and custom fields can all be mapped. Templates are available for the most common entities; see the connector docs.
How fast does the sync run?
ZigiOps syncs continuously on an interval you configure, as short as 10 seconds.
How much does a ServiceNow–Jira integration cost?
ZigiOps is licensed per workflow, from €500 a month billed yearly, so cost does not rise with ticket volume. Cloud hosting, implementation and a free proof of concept are included. See the pricing page.
Can I try it on my own ServiceNow instance?
Yes. You can connect any ServiceNow instance, including a developer instance, in the free trial. A safe test mode validates field mappings and rules on real data before go-live, and you can also ask for a free proof of concept.
How does ZigiOps compare with Exalate and ServiceNow IntegrationHub?
Script-based tools such as Exalate give you control through Groovy scripts. ZigiOps gives you control through a visual console and is licensed per workflow. IntegrationHub's Jira spoke is built and maintained inside ServiceNow. See ZigiOps vs Exalate and our guide to choosing a Jira–ServiceNow integration tool.
Show us your ServiceNow–Jira process.
Book a demo and we'll connect your ServiceNow and Jira instances in real time.