Zendesk-Jira Integration: Methods, What to Sync, and How To Set It up in 2026
Zendesk and Jira are often used in conjunction, since each is specialized for specific teams and their work. Many workflows need to jump the gap between these tools, which usually involves someone copying and pasting data back and forth, booking alignment meetings, or hunting for status updates across tools. Without an effective way to close that gap, workflows and escalations run into significant friction.
In this guide, you’ll learn about integrating Zendesk and Jira, including what options are available, what you can sync, and common use cases. If you’ve already picked Unito and want the step-by-step walkthrough, see how to set up a Zendesk Jira integration with Unito.
Overview: Zendesk-Jira integration
| Zendesk Support for Jira integration | One-way automation (e.g., Zapier) | Two-way sync (e.g., Unito) | |
| Sync direction | Two-way. | One-way, trigger-based automation. | Two-way. |
| Real-time or batch | Near real-time. | Real-time. | Real-time. |
| Field mapping depth | Limited. Shows a few fields from Jira in Zendesk. | Standard fields; custom fields and attachments usually not supported. | Standard fields, custom fields, comments, attachments, hierarchy mapping. |
| Setup time/effort | Low | Low. No-code with limited configuration. | Low. No-code setup. |
| Best for | Ticket escalations. | Simple visibility and handoffs. | Seamless collaboration across teams. |
Why integrate Zendesk and Jira?
Integrating Zendesk and Jira closes the gap between customer success teams and software developers. Usually, this is best suited to managing ticket escalation workflows, allowing customer success to automatically escalate tickets to Jira with all relevant context. But no matter what the use case, this integration creates the following benefits:
- Fewer licenses: Teams that frequently collaborate across Zendesk and Jira often need licenses in both tools. The right integration can eliminate these doubled licenses, saving you on tool budget you can reallocate elsewhere.
- Seamless collaboration: Without an integration, handoffs between Zendesk and Jira add friction to your workflows that can manifest in lost time, late updates, and missed SLA targets. With the right integration, these handoffs are handled automatically.
- Smoother workflows: Handoffs aren’t the only time collaboration across Zendesk and Jira can be challenging. Getting updates from each tool, checking on ticket status, and validating development work all become easier with an integration.
- Better reporting and visibility: The work happening in Zendesk and Jira often contribute to larger workflows, but reporting on that work can be challenging. With an integration, teams can choose to report on that work in either Zendesk or Jira, both tools, or a third tool.
- Real-time updates: Working across tools brings delays as teams wait for information to travel the gap between tools. The right integration updates work items in Jira and tickets in Zendesk automatically to match the work happening in either tool. No waiting around for updates.
Integration depth between Zendesk and Jira
Not every integration between Zendesk and Jira is created equal. One of the key differences between them is integration depth (i.e., how much they can sync).
Work item previews
Some integrations create a read-only link between tools. A Jira work item, for example, might turn into a small panel in a Zendesk ticket, listing a few fields like due dates, assignees, and status. You can’t interact with the Jira work item or update it by working in Zendesk. This kind of integration is good for keeping visibility on work happening in other tools, but doesn’t enable cross-tool work without manually moving data over.
Standard fields in Zendesk and Jira
Zendesk-Jira integrations usually support most, if not all, standard fields. “Standard” means a field is already built into the tool, with little to no customization involved. Due dates, assignees, and descriptions are examples of standard fields.
Most standard fields can be mapped automatically, though some might require a bit of extra input. Statuses that are slightly different across tools (e.g., “To Do” and “Backlog”) might need to be mapped manually.
Custom fields in Zendesk and Jira
Both Zendesk and Jira have custom fields, which allow you to tailor your workspace to your workflows. Jira’s custom fields cover single-select, multi-select, text, number, date picker, user picker, and more. Zendesk’s custom fields include checkbox, date, decimal, drop-down, multi-line, multi-select, and lookup.
Not all integrations can sync custom fields, since they require more transformation than standard fields. Some platforms might handle a few fields while others support most of them.
Comments and notes
Comments and notes are essential to workflows, especially when handoffs are involved. A customer support agent’s escalated ticket is full of context from the customer, from other agents, and from customer-facing documentation. A developer’s Jira ticket might include clarifying questions that guide the work they’ll do after an escalation.
Integrations that support comments and notes help maintain context through escalations and handoffs as teams work across tools.
Attachments between Zendesk and Jira
Attachments allow teams to share deliverables, briefs, and context. Not all integrations can sync attachments, and those that do don’t necessarily all sync integrations in the same way.
Unito, for example, can support attachments in one of three ways: linked, copied, and streamed attachments.
- Linked attachments create a hyperlink in synced work items. When you click on the link, it opens the original attachment in the tool it came from.
- Copied attachments make the same attachment visible in multiple tools.
- Streamed attachments create a unique page for each attachment, independent of either tool.
Hierarchies: Jira epics, work items and sub-tasks
Tools like Jira have hierarchies, which are relationships between levels of work items. In Jira, for instance, the default hierarchy is Epic→Work Item (e.g., Story, Task)→Sub-task. But you can also customize this to something like Theme→Feature→Epic→Story→Bug→Sub-task for an agile product development workflow.
Integration platforms that don’t support hierarchies treat all work items like they’re the same, making it difficult to keep track of your work.
The 3 most common methods for setting up a Zendesk-Jira integration
Zendesk Support for Jira integration
Zendesk’s built-in integration for Jira allows Zendesk agents to do two things:
- Create Jira work items from a Zendesk ticket.
- Link a Zendesk ticket to an existing Jira work item.
These options are shown as buttons in Zendesk tickets. Once an agent clicks either of them, this integration adds a panel to a Zendesk ticket that shows fields from the associated Jira work item, with a link to see more fields. Zendesk agents can customize the fields that show up in this panel, surfacing only the most relevant information for their needs.
Best for: Ticket escalations between Zendesk and Jira that require a limited amount of back-and-forth.
One-way automation (e.g., Zapier)
Third-party automation tools like Zapier use trigger-action logic to automate actions across Jira, Zendesk, and hundreds of other tools. These actions include automatically creating work items in Jira to match Zendesk tickets or updating a specific field in Zendesk when a similar field is changed manually in Jira.
These automation platforms are best suited to linear workflows, like approvals and escalations, that don’t require much back-and-forth. They cover hundreds, if not thousands of tools, and usually a large number of fields, too. But each automation you build with these tools typically only covers a single action. Either it creates a work item or updates a single field. That means you can rarely cover every step in a workflow without creating (and managing) multiple automations.
Best for: Automating high-volume work item creation between Jira and Zendesk with minimal need for visibility or collaboration.
Two-way sync (e.g., Unito)
A two-way (or bidirectional) sync platform like Unito creates relationships between Jira work items and Zendesk tickets, keeping everything up to date as you work. Items are automatically created to match the ones you create manually, and fields are continuously updated in both tools.
Two-way sync platforms typically offer deep integrations that cover most, if not all, standard and custom fields, attachments, comments, and more. Some platforms can even sync hierarchies between tools. These deep integrations can handle all kinds of workflows, from simple approvals to handoffs and true cross-functional collaboration.
Best for: Working seamlessly across Jira and Zendesk with full visibility and no doubling up on tool licenses.
How to choose a Zendesk-Jira integration
When choosing a Zendesk-Jira integration, consider the following criteria.
One-way or two-way
Not every workflow needs a bidirectional sync. If most of your workflows fit that category, then you’ll want to consider one-way automations or similar solutions. If your workflows need true, seamless collaboration, then you’ll want to consider a two-way sync instead.
Custom field and custom object support
Not every integration platform can handle custom fields or objects. If your workflows rely on tools with extensive customization, you need an integration that can support that. Otherwise you’ll be constantly relying on workarounds that eat up more time and energy than the integrations save.
Real-time or scheduled updates
Real-time updates mean your teams always have the most up-to-date information when they work, but not all workflows require this. Most integration platforms push changes in batches, and that may be enough for simple handoffs.
API limits in Zendesk and Jira
An API (Application Programming Interface) surfaces information in a tool so integrations can sync it to other tools. But some tools have API limits, meaning only a certain amount of data can be pulled over a specific period. If your use case involves a massive amount of data, it’s worth seeing if these limits exist and how different integration tools circumvent them.
Who can set it up
Some integration platforms are more complex, meaning you need a team with technical skills to set them up. Others can be deployed by the average business user. One approach isn’t necessarily better than the other, it’s just a matter of which one fits your organization best. A larger company with the technical resources to spare can pick any type of deployment, but smaller teams might want an integration anyone can deploy.
How each integration handles errors
Not every integration platform handles errors the same way. Some stop trying to sync data the moment they run into an issue. Others keep trying to sync, potentially creating duplicate items with each failed attempt. When researching an integration platform, try to find documentation about how errors are handled so you know what to expect.
Security and data residency
Since an integration platform might have access to sensitive, proprietary data, security is essential. Researching a platform’s security certifications and frameworks gives you a sense of how secure your data will be. It can also ensure you use a platform that meets any specific security requirements you have, whether that’s due to the jurisdiction you operate in (e.g., CCPA) or your industry (e.g., HIPAA).
Pricing model of each integration option
A platform’s pricing model should be as important of a consideration as that platform’s capabilities. Using the wrong pricing model can quickly lead to ballooning costs as you use an integration more and more. Consider whether a per-task, per-connector, per-user, or a per-item-in-sync model makes the most sense for your needs.
Use cases for a Zendesk-Jira integration
Ticket escalation from Zendesk to Jira
If you offer a software product or technical service, you’ll get support tickets that your frontline agents can’t resolve. These tickets get escalated to software developers, IT professionals, or other technical roles. The gap between the platform where tickets are first received (Zendesk) and the platform where the work to resolve them is planned (Jira) can be difficult to cross. Integrations close that gap, automatically syncing questions, comments, and ticket status.
AI context for Jira’s agents
Jira has built-in AI agents that allow project managers, salespeople, and software developers to outsource repetitive tasks. But these agents have one big flaw: they typically only have access to the context in Jira. An integration can pull relevant context from both tools for Jira’s AI agents, ensuring tasks are executed more accurately and you get better answers.
Feature request handoff
Whether they come from customers, prospects, or even a public request forum, feature requests can improve your product or service tremendously. But the people who notice the requests are rarely the same as the ones working on them. Integrating Jira and Zendesk allows feature requests to be handed off without any context going missing in the transfer. With the right platform, you can even have feature requests created in Jira automatically when tickets in Zendesk go unresolved.
Priority and SLA routing
An integration can pair Zendesk tickets with Jira work items, maintaining priority across tools. That means teams in both Jira and Zendesk can track progress using the same SLA clock, preventing misunderstandings.
Incident management: one outage, many Zendesk tickets
When an outage produces dozens of tickets about the same problem, Zendesk agents shouldn’t have to escalate every single ticket related to that outage manually. By integrating the two tools, any Zendesk ticket with a tag that represents that outage will automatically get synced to Jira, populated with any additional context from customers.
Zendesk-Jira integration best practices
No matter which integration you pick, consider the following best practices.
- Start with a small pilot project between a few Zendesk tickets and Jira work items. This allows you to test an integration and adjust it before you deploy it more broadly.
- Evaluate the results of a pilot project before implementing integrations at scale. Look for places where they save you time, where they struggle, and any workarounds you’ve had to implement.
- Consider whether your chosen integration platform is accessible enough for business users or whether you need to restrict it to technical teams.
- Regularly review the integrations you use, at least yearly. Compare capability, price, and connector availability with other vendors.
- Use built-in integrations where possible, at least initially, and enhance them with third-party integrations as your needs start to evolve.
What breaks and how to fix it
Jira comments never reach the customer
This is a Zendesk rule, not a failed sync. Comments from other tools can’t be synced as public comments in Zendesk, so a developer’s Jira reply always lands as an internal note. Agents still have to write the customer-facing reply themselves. The opposite direction needs a deliberate choice. Only internal notes sync to Jira by default, but you can include Zendesk public replies too. Turn that on only if engineers need the customer’s own words, because it also sends every customer message into Jira.
Attachments are missing from synced tickets
First, check comment visibility. Zendesk attachments are attached to comments, so Unito applies the same sharing restrictions to both. A flow that only syncs private comments will only sync private attachments. A screenshot the customer attached to a public reply won’t appear in Jira until public comments are in the flow. File sizes can also impact attachment syncing. Zendesk caps a single inbound email or web form attachment at 50MB, which is much smaller than Jira Cloud’s default.
Jira fixes ship but Zendesk tickets don’t update
It’s possible the Zendesk ticket was closed while engineering was still working. A closed ticket can’t be altered or reopened, and any response to it creates a follow-up ticket instead. If your Zendesk account permanently closes tickets after a set period, Unito can’t reopen them. That’s a limitation with Zendesk’s API. As a workaround, you can keep escalated tickets in On-hold or Pending instead of Solved, so the auto-close timer doesn’t run out before the Jira work item does.
Custom Zendesk statuses won’t map to Jira
Unito doesn’t support custom Zendesk statuses, so status mapping only works with the standard set. Zendesk also has one-way transitions of its own. Once a ticket’s status changes from “New,” it can’t return to “New,” and “Closed” can’t be set manually. Don’t map a Jira status like “Reopened” or “Backlog” to “New.” Map Jira’s workflow to “Open,” “Pending,” “On-hold,” and “Solved,” and let Zendesk handle “Closed.”
Description edits don’t make it into Zendesk
Zendesk has no real description field. Unito syncs the ticket’s first comment as the description, and because Zendesk comments can’t be edited, Unito can’t update them. A Jira description rewritten after the first sync won’t show up in Zendesk. The same applies to Zendesk-side edits. Edited comments don’t sync, because Unito only syncs new comments. If a Jira work item starts the sync, finish writing its description before the flow picks it up.
Assignees don’t sync
Zendesk only accepts full agents as assignees. Tickets can’t be assigned to light agents or collaborators, so a Jira developer who has only a light agent seat in Zendesk has no valid match. Some Zendesk rules also depend on this field. A ticket can’t be set to “Solved” without an assignee, so a flow that clears the assignee while moving a ticket to “Solved” can fail. Map Jira assignees only to users who hold full agent roles.
The Organization field won’t map
This field is simply unsupported. Unito can’t sync Zendesk’s Organization field. If Jira needs to know which customer account an escalation came from, copy the organization into a custom ticket field or tag in Zendesk with a trigger, then map that field to a Jira label or custom field.
A large backfill syncs slowly
Zendesk’s API throttles bulk pulls. Unito can only pull 1,000 Zendesk tickets at a time, which slows syncs of large batches, and every account is bound by its plan’s rate limit. Zendesk Suite ranges from 200 requests per minute on Team to 2,500 on Enterprise Plus. Use rules to limit the first sync to open, escalated tickets instead of years of solved ones, and expand the scope after the flow is stable.
Setting up a two-way sync with Unito
- Connect tool accounts to Unito: After signing up for Unito, click +Create Flow and connect Zendesk and Jira.
- Choose flow direction: Flow direction tells your Unito flow where you need new 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 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 Jira with fields in Zendesk. 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.
Want to see what Unito can do?
Meet with a Unito product expert and see the impact Unito can have on your workflows.
What you can sync between Zendesk and Jira
| Zendesk field | Jira equivalent | Sync direction |
| Assignee | Assignee | Two-way |
| Attachment | Attachment | One-way |
| CC (copied user) | User Picker* | Two-way |
| Checkbox* | Checkbox* | Two-way |
| Comment | Comment | Two-way |
| Created At | Date/Time* | Two-way |
| Credit Card Number* | Number* | Two-way |
| Date* | Date/Time* | Two-way |
| Decimal* | Number* | Two-way |
| Description** | Description | Two-way |
| Dropdown* | Single-Select* | Two-way |
| Due Date | Due Date* | Two-way |
| Group | Team | One-way |
| Link to Ticket | Link to Issue | One-way |
| Multi-Line* | Text Field* | Two-way |
| Multi-Select* | Multi-Select* | Two-way |
| Numeric* | Number* | Two-way |
| Priority | Priority | Two-way |
| Regex* | Text Field* | Two-way |
| Requester | Text Field* | Two-way |
| Status | Issue Status | Two-way |
| Subject | Summary | Two-way |
| Submitter | Reporter | Two-way |
| Tag | Label | Two-way |
| Text* | Text Field* | Two-way |
| Ticket Number | Issue Number | One-way |
| Ticket Type | Issue Type | One-way |
| Updated At | Date/Time* | One-way |
*Custom field.
**Zendesk doesn’t have a dedicated description field, but the first comment in a Zendesk ticket can be synced as the description in Jira.
FAQ: Zendesk-Jira integration
What are the key differences between Jira and Zendesk?
Zendesk is a help desk, built around tickets from customers and the agents who answer them. Jira is a work tracker, built around work items that developers plan in sprints. Support teams live in Zendesk and engineering teams in Jira, which is why an escalation needs an integration to carry the ticket’s context between them.
Does Zendesk have a native Jira integration?
Yes, the Zendesk Support for Jira integration allows agents to automatically create Jira work items from Zendesk tickets or link tickets to existing work items. Developers can also reply to Zendesk tickets without leaving Jira. This integration also has near real-time field syncing and updates Zendesk tickets when a linked Jira work item’s status changes.
What’s the difference between Zendesk’s built-in Jira integration and a two-way sync platform?
The Zendesk Support for Jira integration attaches tickets to Jira work items, and teams in both tools can keep up on progress through their own tools. Two-way sync platforms such as Unito, Exalate, or Getint create and maintain paired records using rules and field mappings, so issues can be created automatically without an agent acting on each ticket. The tradeoff is setup. The native app is quicker to install, while sync platforms need upfront configuration but less manual work afterward.
Can multiple Zendesk tickets be linked to one Jira work item?
The Zendesk Support for Jira integration can link one Jira work item with up to 200 Zendesk tickets. Most other integration solutions typically pair a single Zendesk ticket with a single Jira work item.
Does the integration work with Jira Service Management?
Most platforms, Unito included, support Jira Service Management as well as Jira Cloud and Data Center. There might be some differences in field mappings and rules when syncing Zendesk with Jira Service Management, but it’s generally the same functionality.
Which Zendesk plan do I need?
Zendesk’s built-in Jira integration is available on Support Team, Professional and Enterprise, and on every Suite plan from Team to Enterprise Plus. Every Zendesk plan with API access can connect to an integration platform, but API capacity depends on the plan. Here’s that capacity per plan:
- Team: 200 API requests per minute.
- Growth: 400 API requests per minute.
- Professional: 400 API requests per minute.
- Enterprise: 700 API requests per minute.
Zendesk also offers a High Volume API add-on that increases API requests to 2,500 per minute.
Can I automatically escalate Zendesk tickets to Jira?
Not with Zendesk’s built-in integration for Jira. This integration requires that Zendesk agents manually click a “Create Issue” or “Link Issue” button whenever they want to escalate a ticket to Jira. Third-party integration solutions can automatically create Jira work items based on triggers you set up, like specific tags, priority, or reporters.
What happens when a customer replies to a closed ticket that’s linked to Jira?
This depends on the integration solution you use. In Unito, for example, the reply won’t reach the synced ticket. Responses to a closed ticket will create a follow-up ticket, which itself isn’t paired to the original Jira work item the first ticket was synced with.
Can I sync Zendesk custom fields to Jira?
Yes, but not all of them have clean equivalents in Jira. Text, multi-line, dropdown, date, and numeric fields all have direct equivalents in Jira, specifically the short text, paragraph, select list, date picker, and number fields. Zendesk’s checkbox field is a binary, true-false field, while Jira’s checkbox has multiple options. Zendesk’s regex field, meanwhile, might not map cleanly to Jira’s text fields.
How much does a Zendesk-Jira integration cost?
This depends on the integration solution you use and its pricing model. Per-task automation tools scale with volume, while per-connection platforms like Exalate or Getint charge by the number of integrations you use. Two-way sync platforms like Unito typically price by items in sync.