- What support and product teams get from the link
- Permissions and browser settings to sort first
- Installing Zendesk Support for Jira
- Field syncing runs one way
- The v2 Jira app is being withdrawn
- What a good escalation looks like
- Other ways to pass tickets to Jira
- My advice for the support-to-dev handoff
- Frequently asked questions
Install the Zendesk Support for Jira app inside Jira from Atlassian's app directory, enter your Zendesk subdomain and authenticate. Agents can then create or link Jira issues from a Zendesk ticket. You'll need administrator permissions in both tools. Zapier is the connector alternative if you want a simpler one-way route.
What support and product teams get from the link
The Zendesk Support for Jira integration lets agents link or create Jira issues from a Zendesk ticket, so support and product can both track progress on the same problem. A single Jira issue can be linked to up to 200 tickets, which is how you show developers that one bug is hitting a lot of customers.
It supports Jira Cloud and Jira Data Center. It isn't supported on the Jira Cloud mobile app. Jira Server installs keep working but are no longer supported, because Atlassian has ended support for Jira Server.
Permissions and browser settings to sort first
- Administrator permissions in both Jira and Zendesk Support.
- Membership of the jira-administrators and jira-software-users groups.
- The reporter field on the Create Issue screen.
- Third-party cookies enabled, or jiraplugin.zendesk.com and your Jira subdomain added to the exceptions.
Firefox can make the Jira app load incorrectly because of Jira's security headers, so Zendesk suggests another browser such as Chrome for setup.
Installing Zendesk Support for Jira
- In Jira, click Apps in the top navigation bar and select Explore more apps.
- Search for Zendesk, open Zendesk Support for Jira, click Get app, then Get it now.
- When the success notice appears, click Configure and enter your Zendesk subdomain.
- Leave the dedicated Zendesk user option selected, click Authenticate, then Allow, and sign in to Zendesk in the second window.
- On the app settings page, choose the details to display in linked Jira issues and click Save.
- In Zendesk, open a ticket and use the Jira app in the sidebar to create or link an issue.
Keep that dedicated user. By default it's created so escalations from Jira don't appear to come from the admin who set things up, which matters when that admin leaves.
The issue form has default fields that can't be removed: Project, Issue type, Reporter, Assignee, Summary and Description. Admins can add other compatible Jira fields on top.
Field syncing runs one way
Field syncing gives near real-time data sync by mapping Jira issue fields to ticket fields, so agents see status changes without opening Jira. Zendesk lists no bidirectional sync as a limitation, so don't expect a change made on the ticket to update the Jira field.
The v2 Jira app is being withdrawn
Zendesk announced in its Help Center on 6 Nov that it's delisting the new v2 Jira app and re-listing the original, removing the migration path to v2. For now (as of Nov 2026), existing users don't need to change anything, but v2 customers will later be asked to move to the updated integration. If you're installing now, check which version you're getting and expect another move if you're on v2.
What a good escalation looks like
Picture a customer reporting a checkout error. The agent opens the ticket, uses the Jira app in the sidebar to search for an existing issue, and links it if one's there. If not, they create one with a clear Summary and the steps in the Description. Every later ticket about the same error gets linked to that issue, and the mapped status field tells agents when it's fixed.
Other ways to pass tickets to Jira
Zapier lists a template that creates issues in Jira Software Cloud from new Zendesk tickets, which suits a simple one-way handoff.
Zendesk has also added a Jira Service Management connector to action flows. It uses OAuth 2.0 and manages requests rather than Jira Software issues, so it's for service teams, not developer backlogs.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
If you're still choosing your stack, see my roundups of Zendesk alternatives and help desk software for small businesses.
My advice for the support-to-dev handoff
Install the native app, keep the dedicated user, and train agents to link tickets to an existing issue before they create a new one. That's what makes the 200-ticket count useful: developers see how many customers a bug is hurting. Map the two or three fields agents ask about most, and leave the rest in Jira.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Where do I install the Zendesk Jira integration?
In Jira, from Atlassian's app directory: search for Zendesk Support for Jira and click Get app.
Do I need to be an admin?
Yes, administrator permissions in both Jira and Zendesk Support.
How many tickets can link to one Jira issue?
Up to 200 Zendesk Support tickets per Jira issue.
Does it sync both ways?
Field syncing maps Jira issue fields to ticket fields, and Zendesk lists no bidirectional sync as a limitation.
Does it work with Jira Server?
It keeps working on existing installs but is no longer supported. Jira Cloud and Data Center are supported.
