ServiceNow-Jira Integration: Methods, What to Sync, and How To Set It Up in 2026
ServiceNow and Jira serve different functions but overlap in workflows like ITSM and software development. In most organizations, these tools aren’t integrated, meaning someone has to manually copy and paste updates back and forth between them or teams have to communicate exclusively in other channels.
In this guide, you’ll learn about integrating ServiceNow and Jira, including what options you have available, what you can sync, and common use cases.
Market overview: ServiceNow-Jira integration
| ServiceNow’s Jira Spoke | One-way automation (e.g., Zapier) | Two-way sync (e.g., Unito) | |
| Sync direction | Primarily one-way, inbound to ServiceNow. Two-way syncing requires custom webhooks and Flow Designer work. | One-way, trigger-based automation. | Two-way. |
| Real-time or batch | Real-time. | Real-time. | Real-time. |
| Field mapping depth | Standard fields supported via Flow Designer. Custom fields and reference fields usually need scripting. | Standard fields; custom fields and attachments usually not supported. | Standard fields, custom fields, comments, attachments, hierarchy mapping. |
| Setup time/effort | High. Requires Flow Designer expertise, business rules, and scripts for anything beyond simple inbound flows. | Low. No-code with limited configuration. | Low. No-code setup. |
| Best for | Teams already on ServiceNow needing basic, simple inbound Jira connectivity. | Simple visibility and handoffs. | Seamless collaboration across teams. |
What you can actually sync between ServiceNow and Jira
Integration solutions for ServiceNow and Jira aren’t all created equal. One of the main differences between them is integration depth (i.e., how much data they can sync).
Work item previews
This is the most basic level of integration. Instead of actually moving data from Jira into ServiceNow (or vice-versa) integrations at this level only give you a snapshot of what’s happening in one tool. A Jira work item, for example, might show up in ServiceNow as a panel that shows little more than the name of the work item, its status, and its assignee. You can’t update anything in Jira by making changes in ServiceNow. This level of integration is suitable for workflows that only need extra visibility rather than seamless collaboration between tools.
Standard fields
Most integrations go beyond just showing work item previews to supporting some, if not all, standard fields. “Standard” means the field is built right into the tool, with little to no configuration or customization. Fields like due dates, assignees, and descriptions are all examples of standard fields. Integrations can map similar fields between ServiceNow and Jira automatically while others, like statuses, might need some transformation between tools.
Custom fields
Both ServiceNow and Jira have custom fields that allow you to customize them to your specific workflows. Jira’s custom fields include single-select, multi-select, text, number, date picker, user picker, and more. ServiceNow custom fields include choice, reference, table, and date/time fields.
Not all integrations support custom fields. When researching an integration solution for ServiceNow and Jira, consider whether it can handle some, most, or all of the custom fields you need.
Comments and notes
Comments and notes are essential to your workflows; they’re how you communicate on projects, manage handoffs, and get essential context. A developer’s comment might request specific context before their work can begin, a customer support agent’s note might give insights into ticket priority, and so on. Some integrations don’t support comments and notes, which means your teams will have to come up with workarounds to communicate outside of Jira and ServiceNow.
Attachments
Attachments allow teams to share deliverables, briefs, screenshots, and more. Attachment support isn’t default with most integrations, and the way an integration solution handles attachments is almost as important as having support at all.
Unito, for example, can support attachments in three different ways, depending on the integration you’re using:
- Linked attachments create a hyperlink in synced work items. Clicking on the link opens the original attachment in the tool it came from.
- Copied attachments make the exact same file visible in multiple tools.
- Streamed attachments create a unique webpage for each attachment, accessible independent of either tool.
Hierarchies
Both ServiceNow and Jira have hierarchies, which are relationships between levels of work items. ServiceNow, for example, can have user/manager hierarchies, nested location fields, business application to server hierarchies, and more. Meanwhile, Jira has a default hierarchy of Epic→Work Item→Sub-task, but you can also build your own. For example, a custom Jira hierarchy might be Theme→Feature→Epic→Story→Bug→Sub-task.
Integration platforms that don’t support hierarchies treat all work items exactly the same, which makes it difficult to track workflows across tools.
The 3 most common methods for setting up a ServiceNow-Jira integration
ServiceNow’s Jira Spoke
The Integration Hub is ServiceNow’s built-in platform for integrating with tools like Jira. Pre-built spokes frame most of each integration’s capabilities, though extra coding, budget, and time are usually required to deploy them if you have more complex needs. ServiceNow’s Jira Spoke brings data from Jira into ServiceNow, in just one direction, by default. But with custom development work, you can set up a two-way sync between ServiceNow and Jira.
The ServiceNow Integration Hub supports over 175 Spokes (i.e., tools) and thousands of actions. Pre-built templates can handle common use cases, like notifying teams of work happening in other tools, sharing documents, managing access, and more.
Because the Integration Hub is embedded in ServiceNow, it’s a common first choice for integrating ServiceNow and Jira. But it takes a significant amount of customization to support more complex workflows.
Best for: Ticket escalations and software development workflows in organizations that have IT resources for extensive customization.
One-way automation (e.g., Zapier)
Third-party automation tools like Zapier use trigger-action logic to handle automations across ServiceNow, Jira, and hundreds of other tools. The actions you can automate with Zapier include creating work items in Jira to match records in ServiceNow or updating a specific field in ServiceNow when a similar field is changed manually in Jira.
One-way automations are best-suited for managing linear workflows, like approvals, escalations, and other handoffs. Because they cover such a wide range of tools, they can be broadly applicable across your organization, not just for pairing ServiceNow and Jira.
The automations you can build with these tools are relatively simple, typically covering a single action. Either it creates a work item or updates a single field. Covering an entire workflow with these integrations usually requires chaining multiple automations together.
Best for: Automating simple handoffs between ServiceNow and Jira with little need for back-and-forth.
Two-way sync (e.g., Unito)
A two-way sync platform like Unito creates relationships between Jira work items and ServiceNow records, keeping everything up to date as you work. Work items are created automatically to match the ones you manually open in your tools, and fields are updated constantly as you work.
Two-way sync platforms typically offer deep integrations that cover most standard and custom fields. They usually also support attachments, comments, and more. Some even maintain hierarchies and relational fields between ServiceNow and Jira. These deep integrations can support simple and complex workflows, from approvals to cross-department handoffs and true cross-functional collaboration.
Best for: Working seamlessly across ServiceNow and Jira with full visibility and no doubling up on tool licenses.
Use cases for a ServiceNow-Jira integration
Customer support ticket escalation
When customer support agents run into tickets they can’t handle, the tickets are escalated to a more technical team, like software developers or IT professionals. These teams typically work in different tools, meaning the initial ticket might be handled in ServiceNow while technical teams will work on it in Jira. The gap between these tools is where important context and follow-ups go missing. Integrating ServiceNow and Jira closes that gap and improves collaboration between these teams.
ITSM
ITSM has similar challenges as customer support ticket escalation, with success metrics often being based on the speed at which tickets are resolved, the number of tickets resolved in a specific period, and the smoothness of escalations. A ServiceNow-Jira integration doesn’t just make escalations smoother, it ensures all the context a ticket has in ServiceNow lands in Jira without any manual copying and pasting. Tickets land in Jira, where IT teams can work on them, and when they’re closed, teams working in ServiceNow find out automatically.
AI context
Both ServiceNow and Jira have built-in AI agents that take action autonomously based on data in these platforms. But they both have one main limitation; they only have access to the data in their own platforms. Jira’s Rovo agents only pull from Jira work items. ServiceNow AI only pulls from ServiceNow records. An integration between these tools makes that context broadly available to all your AI agents, meaning they’re more accurate and they’ll succeed on more tasks.
Setting up a two-way sync with Unito
- Connect tool accounts to Unito: After signing up for Unito, click +Create Flow and connect ServiceNow and Jira.
- Choose flow direction: Flow direction tells your Unito flow where you need work items created. Most Unito flows are two-way, meaning they automatically create work items in both connected tools.
- Set rules: Unito rules use trigger-action logic to filter out work items you don’t want synced or to automate certain actions. To build a rule, choose a trigger Unito should look for and the action it needs to take.
- Map fields: In most flows, Unito can automatically map fields in ServiceNow with fields in Jira. From there, you can customize field mappings to match statuses across tools, send data from some fields to fields specific to your workflow, and more.
- Launch your flow: Once you map your fields, your flow is ready to launch. After an initial sync, Unito will check for changes in real-time.
FAQ: ServiceNow-Jira integration
Does ServiceNow integrate with Jira for free?
Some integration platforms like Zapier have free options for integrating ServiceNow and Jira, but they typically only support a few actions or a few work items. For complex, enterprise-grade workflows, free integrations aren’t going to cut it. ServiceNow’s built-in integrations require either a Professional Enterprise plan, and the integration for Jira is a premium add-on.
Can I sync ServiceNow tickets with Jira work items?
Yes, you can sync ServiceNow tickets with Jira work items. The most popular ways of doing this include:
- ServiceNow’s Integration Hub: ServiceNow has built-in integrations called Spokes, one of which can sync Jira work items with ServiceNow tickets.
- One-way automation: Tools like Zapier allow you to create one-way automations between ServiceNow and Jira that create new work items to match the ones you create manually or update a single field. You can chain these automations to handle more complex workflows.
- Two-way sync: A platform like Unito builds two-way relationships between work items in Servicenow and Jira, moving updates back and forth between them as you work. These are usually best for maintaining seamless collaboration between tools.
Can non-technical teams set up a ServiceNow-Jira integration without IT?
That depends on the type of integration you use. ServiceNow’s Integration Hub has prebuilt integration templates that can be deployed relatively easily by non-technical teams, but any customization beyond that will usually require IT involvement. One-way automations are easy to build and deploy, but chaining them for more complex workflows creates maintenance and troubleshooting requirements best left to technical teams. Two-way platforms like Unito are best-suited to non-technical teams, since they don’t need any IT involvement to deploy.
How long does it take to set up a ServiceNow-Jira integration?
Depending on the integration method you use, setting up a ServiceNow-Jira integration can take anywhere from minutes to months. The deployment time for an integration generally depends on how technical it is and how much troubleshooting and maintenance it requires.