How to Integrate Jira Service Management with ServiceNow: 4 Methods Explained (2026)
Last updated: October 2026
There are four methods to integrate Jira Service Management (JSM) with ServiceNow: Atlassian's built-in ServiceNow integration in JSM, which exchanges alerts and incidents; ServiceNow's Jira Service Management spoke in IntegrationHub; a two-way sync app from the Atlassian Marketplace; and a standalone no-code integration platform such as ZigiOps by ZigiWave. The right method depends on whether you are syncing alerts or full tickets, who owns the integration, and whether you need comments, attachments and statuses to flow both ways.
Jira Service Management and ServiceNow meet more often than their marketing suggests. An internal IT team runs JSM while a parent company runs ServiceNow. A managed service provider works in ServiceNow while a customer's service desk lives in JSM. A software team takes escalations from a ServiceNow service desk into a JSM project. Each scenario needs a different kind of integration.
This guide explains the four methods, what each one actually syncs according to the vendors' own documentation, and how to choose between them.
The four methods to integrate ServiceNow with Jira Service Management at a glance
| Criterion | 1. JSM built-in ServiceNow integration | 2. ServiceNow JSM spoke | 3. Atlassian Marketplace apps | 4. Standalone platform (ZigiOps) |
|---|---|---|---|---|
| Primary purpose | Alert and incident response | Automating JSM actions from ServiceNow flows | Ticket synchronization | Ticket synchronization across ITSM, DevOps and ITOM tools |
| What syncs | ServiceNow incident events to JSM alerts, JSM alerts to ServiceNow incidents | Whatever your flows do with spoke actions, such as creating customer requests | Requests, incidents, comments, attachments, statuses (varies by app) | Requests, incidents, problems, changes, comments, work notes, attachments, statuses |
| Where it is configured | JSM operations settings plus ServiceNow configuration | ServiceNow Flow Designer | Inside Jira, and often inside ServiceNow too | Separate ZigiOps web console |
| Extra licence | Part of JSM's operations features; check what your JSM plan includes | ServiceNow Integration Hub subscription | App licence | ZigiOps licence per pair of system instances |
| Coding | None | Low-code flows | No-code to scripted, depending on the app | None: 100% code-free |
| Data storage by the integration layer | Alert data held in JSM | Data stays in ServiceNow | Varies by vendor | No transferred data stored |
| Best for | On-call and major incident response | ServiceNow-led teams with Integration Hub | Single JSM and ServiceNow pairs | Enterprise, multi-instance and MSP scenarios |
Method 1: Atlassian's built-in ServiceNow integration in JSM
Jira Service Management includes a native ServiceNow integration, inherited from Atlassian's operations and alerting capabilities (formerly Opsgenie). According to Atlassian's support documentation, "Integrate with ServiceNow", the integration sends ServiceNow incident events to Jira Service Management and forwards JSM alerts to ServiceNow as incidents. Atlassian describes it as bidirectional.
How it works
- In JSM, add a ServiceNow integration from the integrations list and, optionally, choose an assignee team so only that team receives alerts from it.
- Copy the integration key JSM generates.
- In ServiceNow, configure the integration with that key and save it.
- Enter your ServiceNow instance subdomain in the JSM integration settings.
- Configure action mapping: what happens in ServiceNow when someone acknowledges, adds a note to or closes an alert in JSM, and whether JSM alerts from other sources should create ServiceNow incidents.
Strengths and limits
This method is quick to set up and, where your JSM plan already includes the operations features, adds no separate licence. It is excellent for on-call workflows: a P1 incident in ServiceNow pages the right engineer through JSM, and acknowledging or closing the alert updates ServiceNow.
The limit is scope. It is designed around alerts, not around full request or incident records with custom fields, SLAs, comments and attachments. If your goal is to let two service desks work the same ticket in their own tools, this method is not built for that.
One planning note: Atlassian states that Opsgenie's alerting and on-call features are now part of Jira Service Management and Compass, and that existing Opsgenie customers should migrate their data and configurations before April 5, 2027. If your ServiceNow alert integration still runs in standalone Opsgenie, add that migration to your 2026 or early 2027 roadmap.
Method 2: ServiceNow's Jira Service Management spoke
ServiceNow IntegrationHub includes a dedicated Jira Service Management spoke. This is separate from the Jira spoke, which, according to ServiceNow's documentation, does not support Jira Service Desk. The JSM spoke exists to fill that gap.
What the JSM spoke can do
ServiceNow's documentation for the JSM spoke lists actions such as:
- Create a customer request in a specified service desk.
- Look up service desks, service desk IDs and queues.
- Add or remove organizations and customers on a service desk.
- Look up SLA information and subscription status for a service desk.
- Remove customer request participants.
Newer documentation versions also describe Now Assist AI agents for JSM organization and service desk management, available when you install Now Assist for Integration Hub.
Strengths and limits
The JSM spoke is the natural choice for teams that live in ServiceNow, already have an Integration Hub subscription (which the spoke requires), and want to automate specific JSM actions from ServiceNow flows, such as raising a customer request with a supplier who uses JSM.
What the spoke gives you is actions, not a finished synchronization. Keeping a ServiceNow incident and a JSM request aligned over their full lifecycle, with comments, attachments and status changes both ways, means designing and maintaining flows, inbound triggers and correlation logic yourself. That is perfectly doable for a ServiceNow developer, but it is a project rather than a setting.
Method 3: Two-way sync apps from the Atlassian Marketplace
The Atlassian Marketplace has several apps that synchronize Jira and JSM with ServiceNow. They are usually installed in Jira, and some also need a component in ServiceNow.
- Exalate supports real-time bidirectional sync between ServiceNow and Jira, including Jira Service Management, according to its Marketplace listing. The listing states that Exalate must be installed on both sides of the connection. Sync logic is written in Groovy, with an AI assistant called Aida that generates scripts.
- Getint offers a ServiceNow integration for Jira built on Atlassian Forge, with one-way or two-way sync of incidents, service requests and change requests, and lists ISO 27001 and SOC 2 on its Marketplace page.
- OpsHub Integration Manager offers bidirectional ServiceNow sync for Jira Cloud, including comments, attachments and links, aimed at larger multi-project deployments.
Strengths and limits
Marketplace apps are easy to find, easy to trial and billed through Atlassian in many cases. For a single JSM site and a single ServiceNow instance they can be a quick win.
Things to check before committing: whether the app needs installing in ServiceNow as well, how pricing scales (by Jira user tier, by synced item or by connection), whether advanced use cases require scripting, and where the vendor processes and stores your ticket data. Those answers vary a lot between apps.
Method 4: A standalone no-code integration platform
A standalone integration platform runs as its own application between JSM and ServiceNow. It talks to both through their REST APIs, so it does not need to be installed inside either system.
How ZigiOps integrates Jira Service Management with ServiceNow
ZigiOps, from ZigiWave, is a standalone, 100% no-code integration platform that connects ITSM, ITOM, DevOps and CRM tools in real time, without storing any of the transferred data. It is ISO 27001 certified and has no limit on the number of transactions.
For a JSM and ServiceNow integration, the setup follows the ZigiOps documentation:
- Connect Jira Service Management: add Jira as a connected system with its URL and an integration account (API token for Jira Cloud), then enable the JiraSD option in the system's advanced settings so ZigiOps works with service desk requests.
- Connect ServiceNow: add the instance URL and an integration user with read, create and write access to the integrated table, plus read access to the system tables ZigiOps uses to discover your schema.
- Choose entities: for example JSM requests and ServiceNow incidents, or ServiceNow change requests and JSM tasks.
- Configure correlation: store the JSM key in the ServiceNow correlation_id field and the ServiceNow number in a JSM custom field.
- Map fields: use the guided field map, with conditional mapping for values that do not match one to one, such as ServiceNow impact and urgency to JSM priority.
- Set triggers: polling (recommended interval 1 minute) or a listener endpoint for pushed updates.
- Add update operations both ways so comments, work notes, attachments and status changes stay in sync.
ZigiWave also publishes ZigiOps on the Atlassian Marketplace as "No-code ServiceNow integration for Jira Service Management", so JSM admins can find it alongside other options.
Strengths and limits
The standalone approach suits enterprises and service providers that need full ticket synchronization, more than one instance on either side, or integrations with additional tools beyond JSM and ServiceNow, such as monitoring or DevOps platforms. Because ZigiOps is code-free, the integration can be owned by service management leads. Because it stores no transferred data, it is easier to pass through security and privacy reviews.
The trade-off is that it is another application to deploy, either on-premises on Windows or Linux, or in the cloud. For a single alert-routing use case, Method 1 is simpler.
Which method should you choose?
| Scenario | Recommended method | Why |
|---|---|---|
| Route ServiceNow major incidents to on-call engineers in JSM | Method 1: built-in JSM integration | Designed for alerts, acknowledgements and paging |
| A ServiceNow team raises requests with a supplier that uses JSM, and has Integration Hub | Method 2: JSM spoke | Spoke actions create customer requests from ServiceNow flows |
| One JSM site, one ServiceNow instance, modest volume, Jira admins own the tool | Method 3 or Method 4 | Trial a Marketplace app and a standalone platform and compare pricing and effort |
| Full two-way sync of incidents, comments, attachments and statuses, no scripts | Method 4: ZigiOps | Bidirectional, code-free, standalone |
| An MSP connecting many customer JSM and ServiceNow instances | Method 4: ZigiOps | Each instance pair is configured separately, with no transaction limits |
| Strict data residency or privacy requirements | Method 4: ZigiOps | No transferred data stored, ISO 27001 certified, can run on-premises |
Common JSM and ServiceNow integration patterns
Pattern 1: Service desk to service desk
Two organizations, two service desks. A ServiceNow incident assigned to the partner's group creates a JSM request in the partner's project. Public comments sync both ways, internal notes stay internal, and resolving the JSM request resolves the ServiceNow incident with the right resolution code.
Pattern 2: Service desk to engineering
The ServiceNow service desk escalates to a team that uses JSM as its intake queue, for example an internal platform team. Priority is translated from ServiceNow impact and urgency, and the JSM SLA becomes visible on the incident through a mapped field or work note.
Pattern 3: Alerts to incidents
Monitoring tools send alerts to JSM, where on-call teams triage them. Confirmed incidents are created in ServiceNow for ITIL process tracking. This is where Method 1 shines, and where a platform like ZigiOps can add direct monitoring-to-ServiceNow integrations for tools JSM does not cover.
Pattern 4: Change coordination
Change requests approved in ServiceNow create implementation tasks in JSM or Jira, and their completion updates the change record. This needs full record sync, so Methods 3 or 4 fit best.
Five tips for a smoother JSM ServiceNow integration
- Decide the system of record per field. Who owns priority, assignment and state? If both sides can change everything, you will spend your time resolving conflicts.
- Separate public and internal comments. JSM distinguishes customer-visible replies from internal comments; ServiceNow distinguishes additional comments from work notes. Map them deliberately.
- Use dedicated integration accounts. Filter out their changes in every update rule to prevent loops.
- Map status meaning, not status names. A JSM "Waiting for customer" is usually ServiceNow "On Hold" with a reason, not "In Progress".
- Plan for growth. Today it is one JSM project. Next year it is five, plus a second ServiceNow instance after an acquisition. Choose a method whose cost and effort scale gracefully.
Frequently asked questions
Can Jira Service Management integrate with ServiceNow natively?
Yes. JSM includes a built-in ServiceNow integration that sends ServiceNow incident events to JSM as alerts and forwards JSM alerts to ServiceNow as incidents. It is focused on alert and incident response rather than full ticket synchronization.
Does the ServiceNow Jira spoke work with Jira Service Management?
No. ServiceNow's documentation states that the Jira spoke does not support Jira Service Desk. ServiceNow provides a separate Jira Service Management spoke, which requires an Integration Hub subscription.
Can ZigiOps integrate Jira Service Management with ServiceNow?
Yes. ZigiOps supports both Jira Software and Jira Service Management. You enable the JiraSD option on the Jira connected system and then sync requests, incidents, comments, attachments and statuses with ServiceNow in both directions.
Is ZigiOps available on the Atlassian Marketplace?
Yes. ZigiWave lists ZigiOps on the Atlassian Marketplace, including a "No-code ServiceNow integration for Jira Service Management" listing. ZigiOps itself runs as a standalone application rather than as a plugin inside Jira.
Can I sync JSM SLAs to ServiceNow?
You can sync SLA-related fields and status changes, and the ServiceNow JSM spoke includes an action to look up SLA information. SLA timers themselves are calculated by each platform, so map the fields that matter, such as breach status or due date, rather than trying to share the timer.
Which JSM ServiceNow integration method is best for managed service providers?
MSPs usually need many customer instances, strict data separation and predictable costs. A standalone platform such as ZigiOps fits that pattern because each instance pair is configured independently, no transferred data is stored, and there is no limit on transactions.
Key takeaways
- Method 1, JSM's built-in ServiceNow integration, is ideal for alerts and on-call, not for full ticket sync.
- Method 2, the ServiceNow JSM spoke, provides actions for ServiceNow flows and requires an Integration Hub subscription.
- Method 3, Marketplace apps, can be fast for single-pair setups; check installation footprint, scripting and pricing model.
- Method 4, a standalone platform such as ZigiOps by ZigiWave, delivers full bidirectional, code-free sync with no data storage and no transaction limits.
- Whatever the method, agree field ownership, comment visibility and status meaning before you configure anything.
For more detail, ZigiWave's website includes Jira ServiceNow integration use cases and a ServiceNow incident to Jira issue mapping guide that applies equally to Jira Service Management projects.