Merging Tickets in Jira Service Management
Jira does not support merging issues. It is one of the longest-standing requests from service teams, and every workable answer is a workaround.
Merging duplicates in Jira Service Management
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.
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.
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
Frequently asked questions
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 cannot combine two issues into one. Marketplace apps go further by copying comments across.
Jira Service Management can't merge. Zendesk and Freshdesk, with HubSpot coming soon can.
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 trial14-day free trial. No credit card required.