Ticket Merger

Merge Tickets: Jira Service Management

There's no clean way to merge tickets: Jira has never supported merging issues. It's one of the longest-standing requests from service teams, and every workable answer is a workaround.

See supported platformsMerge duplicates automatically

How to merge tickets: Jira options that actually work

1

Link the duplicate to the original

Use the "duplicates" issue link type so the relationship is explicit and reportable, rather than living in a comment nobody reads.

2

Close the duplicate with a pointer

Resolve it as Duplicate and reference the surviving issue key in the resolution comment, so the reporter knows exactly where the work now lives.

3

Handle the split conversation

This is the real cost. Replies to the closed request keep the conversation on the wrong issue. Automation can nudge the reporter to the surviving issue, and Marketplace merge apps exist to consolidate comments if you need it properly solved.

The uncomfortable part

Linking isn't merging. The customer conversation stays split across two issues, which is the actual problem people are trying to solve.
If duplicates are frequent enough to hurt, that's usually a channel problem: an email address and a portal both creating requests with nothing matching them.
Ticket Merger doesn't integrate with Jira today. This page exists because the honest answer is hard to find.
FAQ

Frequently asked questions

How do you handle duplicate issues in Jira?

How to merge duplicate issues in Jira: you don't. You link one as a duplicate of the other, close it with a comment pointing at the survivor, and keep the original as the single source of truth.

Can you merge tickets in Jira Service Management?

Not natively. Jira links issues as duplicates instead, which leaves both open. Automation rules can close and comment on one side, and Marketplace apps add a merge action, but nothing folds two issues into one the way a helpdesk does.

Is there a merge button in Jira Service Management?

No. Atlassian has never shipped one, and the standard approach is to link the duplicate and resolve it with a reference to the surviving issue.

Can automation merge Jira issues?

Automation can link, comment, transition and close, but it can't combine two issues into one. Marketplace apps go further by copying comments across.

Jira Service Management can't merge tickets. Zendesk and Freshdesk can, with HubSpot coming soon.

On the platforms that do support merging, Ticket Merger finds the duplicate pairs as they arrive and merges them through the native API, so the conversation never splits in the first place.

Start free trial

14-day free trial. No credit card required.

Keep reading

How to Merge Tickets in Any Helpdesk
How to merge tickets in Zendesk, Freshdesk, HubSpot, Zoho Desk, ConnectWise, Help Scout, ServiceNow, Jira and more, with the real limits of each platform.
Combine Duplicate Tickets Without the Manual Hunt
Combining duplicate tickets by hand means noticing them first. Ticket Merger finds the pairs and combines them for you in Zendesk and Freshdesk, automatically.
Duplicate Ticket Detection for Support Teams
Duplicate tickets inflate your volume, split your replies and hide SLA breaches. Here's how automatic duplicate ticket detection finds them the moment they arrive.
How to Merge Tickets in Spiceworks
How to merge tickets in Spiceworks help desk, what happens to the closed ticket, and how to keep an internal IT queue free of the same request twice.
osTicket Merge Tickets: Merging and Linking
osTicket merge tickets and link tickets are different actions. What each one does, what happens to the child thread, and how to decide which one you need.