How to Integrate Zendesk with Jira (Step by Step)

This guide walks the whole setup, step by step — installing and authorizing the app, connecting Zendesk and Jira over OAuth, configuring which fields and comments sync (and in which direction), and then actually linking or creating a Jira issue from a ticket. Every step is verified against Zendesk's and Atlassian's own documentation. One honest note up front: the app's main install actually happens on the Jira side, in the Atlassian Marketplace, and a chunk of the configuration lives in Atlassian's screens — so this guide describes those Jira screens accurately rather than pretending to screenshot them.

Why connect Zendesk and Jira at all

Support and engineering run on different tools for good reasons. Zendesk is built around the customer conversation; Jira is built around the development backlog. The integration's job is to let one ticket and one issue stay aware of each other without forcing either team into the other's tool.

Concretely, a connected setup gives you:

• Escalate a bug from a ticket to a Jira issue — an agent creates a properly-formatted Jira issue straight from the ticket, with the relevant context attached, instead of re-typing it into a Jira board they may not even have access to.
• Keep status in sync — when engineering moves the issue from In Progress to Done, the linked Zendesk ticket can be notified automatically, so the agent knows the fix shipped and can close the loop with the customer.
• Share comments both ways — developers can leave a note on the Jira issue that reaches the agent (and optionally the customer), and agent comments flow into the Jira issue's activity.

The result is a clean escalation path: support stays in Zendesk, engineering stays in Jira, and the link between them carries the status and context. If you're still getting your head around how Zendesk's tickets work in the first place, our Zendesk ticketing system explained guide is a good primer before you wire in a second system.

Before you start: requirements and permissions

A few prerequisites will save you a mid-setup detour. The integration is genuinely free, but it has real access requirements on both sides.

• A Zendesk plan that includes the integration. The native Jira integration is available on Support Team, Professional, or Enterprise, or on the Suite Team, Growth, Professional, Enterprise, or Enterprise Plus plans. In short: Team plan or higher.
• **Admin rights in both systems.** You need administrator access in Zendesk and in Jira to install and connect the app — this is not something an agent can self-serve.
• The right Jira groups. The setup requires membership in the jira-administrators and jira-software-users groups.
• The reporter field on your Create Issue screen. Zendesk's app needs it present, or issue creation will fail.
• Third-party cookies enabled (or whitelist jiraplugin.zendesk.com plus your Jira subdomain). Browser cookie blocking is a common silent cause of "the panel won't load."

Jira Cloud vs. Server/Data Center

This matters before you install. The current Zendesk Support for Jira app supports Jira Cloud and Jira Data Center. It is no longer supported on Jira Server, following Atlassian's end-of-support for that product. It's also not supported inside the Jira Cloud mobile app. If you're on Jira Cloud (the most common case today), you're on the well-trodden path; Data Center works but check the current docs for any self-hosted caveats.

Step 1 — Install the app from the Atlassian Marketplace (Jira side)

Here's the part that trips people up: even though this is a "Zendesk app," the official install starts in Jira, via the Atlassian Marketplace. From your Jira instance, as a Jira admin:

1. Click Apps in the top navigation, then Explore more apps.
2. Search for Zendesk.
3. Find Zendesk Support for Jira (published by Zendesk) and click Get app.
4. Click Get it now to add it to your Jira instance.
5. When the confirmation notification appears, click Configure to start connecting it to Zendesk.

This installs the Jira-side half of the integration. These screens live in Atlassian, so they'll look like the rest of your Jira admin — not like Zendesk. (We're describing them from Atlassian's documentation rather than showing a Jira screenshot, so you're not looking at a fabricated UI.)

Step 2 — Connect and authenticate over OAuth

With the app installed in Jira, the Configure flow links it to your Zendesk account. Still on the Jira side:

1. Enter your Zendesk subdomain (the yourcompany part of yourcompany.zendesk.com).
2. Leave the Create a new dedicated Zendesk user for this integration checkbox selected — it's on by default, and Zendesk recommends it. A dedicated integration user keeps automated actions (synced comments, status updates) cleanly attributed instead of muddying a real agent's activity.
3. Click Authenticate, then Allow to start the OAuth handshake.
4. On the redirected page, sign in to your Zendesk account to authorize the connection.
5. Choose the display details you want to show for linked issues.
6. Click Save.

That OAuth step is what actually ties the two systems together — you're granting the Jira app permission to talk to your Zendesk instance as the dedicated user. Once it's saved, the connection is live in both directions.

Step 3 — Confirm and manage the app in Zendesk Admin Center

Now hop over to Zendesk. The authentication in Step 2 connects the Zendesk-side app automatically, and you manage it from the Admin Center. Go to:

Admin Center → Apps and integrations → Apps → Zendesk Support apps

There you'll find the Jira app listed among your installed apps. This is also where you control who can use it — under the app's Installation settings you can restrict it by role and by group, so only the agents and teams who actually escalate to engineering see the Jira panel in their ticket sidebar.

The screenshot below is this exact area of Zendesk — the Apps and integrations → My Apps page in Admin Center, where installed apps (including the Jira integration) are listed and managed, with the Marketplace button to add more. To be clear about what you're looking at: this is the Zendesk apps admin, where the Jira integration is installed and its access is controlled. The Jira-side configuration from Steps 1–2 happens in Atlassian, not here.

Step 4 — Configure which Jira projects agents can use

By default, agents could create issues into any project. Most teams want to narrow that — you don't want a support agent filing into the finance team's private board. In the app's settings you'll find two controls:

• Allowed projects — list only the Jira projects agents are permitted to create issues in. Everything else is hidden.
• Restricted projects — the inverse: leave most projects open but explicitly exclude specific ones.

Pick whichever is less work for your project layout. Setting this early prevents the most common "why is this bug in the wrong board?" cleanup later.

Step 5 — Set up field syncing (and pick a direction)

Linking a ticket to an issue is useful on its own, but field syncing is where the integration earns its keep — it keeps data points like priority, status, or a custom field aligned across both systems in near real time. You configure it by mapping a Jira issue field to a Zendesk ticket field.

A few things to get right, because field syncing has sharp edges:

• Sync direction is set per field. You decide, field by field, whether data flows Jira → Zendesk, Zendesk → Jira (subject to what each field supports). Importantly, only one mapping is allowed per field — you can't point two sources at the same field.
• **Custom-field values must match exactly.** For dropdown/list custom fields, the values on both sides have to match precisely — spelling, capitalization, and even trailing spaces. A stray space is a classic reason a sync silently does nothing.
• You can't un-sync a field. Once a field is data-synced, that mapping is permanent. Because of that, test field syncing in a sandbox or test environment first rather than experimenting in production.
• It only applies going forward. Field syncing affects tickets and issues created after you turn it on — it won't retroactively reconcile your existing backlog.

Given those constraints, the sane approach is to start with one or two high-value fields (status and priority are the usual picks), validate them in a sandbox, and expand from there.

Step 6 — Understand how comments and status flow

This is the part teams most often misjudge, so set expectations correctly:

• Status updates. When a linked Jira issue's status changes, the agent (and optionally the customer) can be automatically notified — but this requires you to turn on and configure the notification, it's not automatic out of the box.
• Agent → Jira comments. From the Zendesk ticket, an agent uses the Notify button to push a comment to the Jira issue, where it lands in the issue's Activity section. Note that both public and private comments added to the Support ticket are shared with connected Jira issues — so don't put anything in a private internal note that you wouldn't want a developer (or, if it's a public reply, the customer) to see in Jira.
• Jira → agent comments. Developers can comment on linked tickets from within Jira; that comment emails the agent and, if it's public, the customer.

Comment-sync caveats (important)

The two commenting systems are not fully integrated, and pretending otherwise leads to dropped messages. Specifically:

• Zendesk collaborators are not automatically notified of new Jira comments unless they're watching the issue.
• Comments can't be marked as read by other users.
• There is one Jira panel per ticket — a ticket can link to multiple Jira issues, but they share a single panel in the sidebar.

None of these are dealbreakers; they're just the reality of bridging two tools. Treat the comment sync as a convenience for cross-team notes, not as a real-time chat between support and engineering.

Step 7 — Link or create a Jira issue from a ticket

With everything connected, the day-to-day workflow is fast. Open any ticket that needs engineering and find the Jira app panel in the ticket sidebar (in the Agent Workspace). You have two options:

1. Create Issue — file a brand-new Jira issue from the ticket. Select the project, enter the issue details, and optionally copy ticket fields into the new issue so engineering gets the context automatically. The new issue is created in Jira and linked to this ticket in one move.
2. Link Issue — connect the ticket to an existing Jira issue by entering its issue key or URL. Use this when several customers report the same bug: link all their tickets to the one issue.

A single Jira issue can be linked to up to 200 Zendesk Support tickets, which is exactly what you want for a widespread bug — one issue, many linked tickets, and when it's fixed every linked ticket reflects the resolved status.

Step 8 — Watch status updates flow back

Close the loop by testing the round trip. From the Jira side, a developer (or you, for the test) views linked tickets in the issue's Zendesk Support sidebar and can open ticket details directly. Then:

1. Move the linked Jira issue's status forward (e.g. to Done).
2. Confirm the linked Zendesk ticket receives the status notification you configured in Step 6.
3. Check that any synced fields updated on the ticket as expected.

If the status doesn't flow back, the usual culprits are: the notification wasn't enabled, third-party cookies are blocked, or the field mapping was set in the wrong direction. Retrace the matching step.

Limitations to keep in mind

The official integration is solid, but it's deliberately scoped. Set expectations with your team:

• One Jira panel per ticket — multiple linked issues share a single sidebar panel.
• Comment sync is partial — no auto-notification of Jira comments to non-watchers, no read receipts.
• Field sync is one-way per field and permanent — plan mappings before you commit, and test in a sandbox.
• Sync only applies to records created after setup — your existing tickets and issues won't be retroactively linked or synced.
• Platform support is Cloud and Data Center only — Jira Server is end-of-life, and the Jira Cloud mobile app isn't supported.

If you need richer, fully bidirectional sync across many fields and comment threads, that's where third-party integration tools (Unito, Exalate, Getint, and others) come in — at extra cost and extra setup. For most support-to-engineering escalation needs, the free official app is the right starting point. And if you're weighing Jira's own service desk product against Zendesk for support itself, that's a different question entirely — see Zendesk vs. Jira Service Management.

Where AI fits in

Here's something worth sitting with before you celebrate a smooth escalation pipeline: most tickets that get escalated to Jira shouldn't have been. When you actually audit what support sends to engineering, a large share aren't bugs at all — they're "how do I do X," "is this expected behavior," or "where's the setting for Y." They get escalated because the agent didn't have the answer at hand, not because engineering needs to write code. Every one of those is an interruption to a developer's day and a slow, multi-day wait for a customer.

That's the gap an AI agent like Macha is built to close. To be clear about what Macha is: it's an AI agent layer that runs on top of your existing Zendesk — not a help desk, and not a Zendesk or Jira replacement. It reads the customer's actual question, pulls from your connected knowledge base and past tickets, and resolves the answerable ones directly in the ticket — so the only things that reach your Jira escalation path are genuine bugs that truly need engineering. Fewer false escalations, fewer interrupted developers, faster answers for the routine majority.

The honest framing: Macha won't fix a real bug — that still belongs in Jira, exactly as this guide describes. It's only as good as the knowledge you connect to it, and it's another integration to configure. On cost, Macha bills per AI action — any automated step it takes, whether drafting a reply, tagging, or resolving — not per ticket closed, because most useful automation isn't a tidy "resolution," it's work done along the way. If a big slice of your Jira escalations are really just questions in disguise, that's the line where an AI agent pays for itself. You can see how it works on Zendesk or try it — 7-day free trial, no credit card required.

Frequently asked questions

Is the Zendesk Jira integration free? Yes. The official Zendesk Support for Jira app is free and published by Zendesk. You do need a Zendesk plan that includes the native integration (Support Team, Professional, or Enterprise, or Suite Team and above) and admin access in both Zendesk and Jira.

Where do I install the Zendesk Jira app — in Zendesk or Jira? The official install starts in Jira, via the Atlassian Marketplace (Apps → Explore more apps → search "Zendesk" → Zendesk Support for Jira → Get app). During configuration you authenticate to your Zendesk account over OAuth, which connects the Zendesk side. You then manage the app in Zendesk Admin Center → Apps and integrations → Apps → Zendesk Support apps.

Does it work with Jira Cloud and Jira Server? It supports Jira Cloud and Jira Data Center. It is no longer supported on Jira Server (Atlassian ended support for Server), and it doesn't work inside the Jira Cloud mobile app.

How do I link a Zendesk ticket to a Jira issue? Open the ticket, find the Jira panel in the sidebar, and choose Link Issue to connect an existing issue (by key or URL) or Create Issue to file a new one (select a project, enter details, optionally copy ticket fields). One Jira issue can link to up to 200 Zendesk tickets.

Do comments sync between Zendesk and Jira? Partially. Agents push comments to Jira's Activity via the Notify button (both public and private Support comments are shared), and Jira comments can reach agents and customers. But the systems aren't fully integrated — Zendesk collaborators aren't auto-notified of new Jira comments unless they watch the issue, and comments can't be marked as read.

Can I sync custom fields between Zendesk and Jira? Yes, via the field syncing feature — you map a Jira field to a Zendesk field, set the direction per field, and data syncs in near real time. Caveats: custom-field values must match exactly (spelling, case, spaces), a synced field can't be un-synced (test in a sandbox), and syncing only affects records created after setup.

The bottom line

Integrating Zendesk with Jira is a clear sequence: install the free Zendesk Support for Jira app from the Atlassian Marketplace, authenticate the two systems over OAuth (with a dedicated integration user), manage and restrict the app in Zendesk Admin Center → Apps and integrations → Apps → Zendesk Support apps, scope the projects agents can file into, configure field and comment sync (carefully — sync direction is per field and permanent, so test in a sandbox), then create or link Jira issues straight from a ticket and watch status flow back. Mind the real limits — one panel per ticket, partial comment sync, Cloud/Data Center only — and you've got a clean escalation path from support to engineering. And remember the bigger lever: the fewer false escalations you send to Jira in the first place, the more this pipeline is reserved for the bugs that actually need it.

Setup steps verified against Zendesk's and Atlassian's official documentation, June 2026. Both products update periodically — confirm labels and menu paths in your own account before relying on them. Jira-side screens are described from the docs, not screenshotted.