Guide

How to merge tickets in Jira Service Management

For Jira Service Management Cloud · Updated November 2026

Short answer: Jira Service Management Cloud has no built-in merge. You can link two requests as duplicates and close one, copy what matters by hand, or use an app that merges for you. This guide covers all three, plus how to stop duplicates from email in the first place.

Why duplicate requests happen

• The customer writes again instead of replying, usually with a new subject, because nobody answered yet.
• Someone else replies to the thread. A colleague who was CC'd replies, but isn't on the request, so the reply becomes a new ticket.
• Two channels. The customer raises it in the portal and also sends an email.
• Mailbox setup. A forwarding rule or a mail connector that reads the same message twice creates exact copies.

Option 1: merge by hand

This is Atlassian's own recommendation. It works for the occasional duplicate, but takes a few minutes each time.

1. Decide which ticket stays open, normally the older one, or the one an agent is already working on.
2. On the duplicate, choose Link work item → duplicates → the ticket that stays open.
3. Copy anything useful from the duplicate, such as the description, comments and attachments, into an internal note on the open ticket.
4. Add the duplicate's reporter and participants to the open ticket under Request participants, so they keep getting updates.
5. Reply to the customer on the duplicate with the key of the open ticket, then close the duplicate with a resolution such as Duplicate.

The weak spot: if the customer later replies to the closed duplicate, that reply lands on a ticket nobody is watching.

Option 2: flag duplicates with Automation

Jira Automation can't merge, but it can catch likely duplicates as they arrive. A simple rule:

1. Trigger: Work item created.
2. Condition: the request came in by email (or any channel you choose).
3. Lookup work items with JQL such as project = SUP AND reporter = {{reporter.accountId}} AND statusCategory != Done AND created >= -1d AND key != {{issue.key}}.
4. If anything is found: add a label like possible-duplicate and an internal comment listing the keys.

This matches on the customer only, so it also flags a genuinely new question from the same person. Agents still do the merging by hand.

Option 3: stop email duplicates at the source

• Keep the ticket key in the email subject. Replies with the key are added as comments instead of creating new tickets.
• Let CC'd colleagues comment. Check your project's customer permissions and customer sharing settings, so replies from people on the thread can be added to the request.
• Check for one customer with two accounts. Atlassian's guide Resolve duplicate ticket creation from email replies in JSM Cloud covers this case.
• Remove forwarding loops. If your support mailbox forwards to itself or to the Jira address twice, each message is processed more than once.

Option 4: use an app that merges

Several Marketplace apps add a real merge: they move comments, attachments and people, then close the duplicate. They differ in whether they also find duplicates for you, and when.

How Queue Tidy handles it

Queue Tidy compares each new request with the same customer's open requests. A likely duplicate appears under Queues → Duplicates, or merges on its own when the match is near certain. One click moves the conversation (as agent-only notes, with original authors and dates), attachments and the customer to the ticket that stays open, links and closes the duplicate, and tells the customer which ticket to follow. If they reply to the closed one later, the reply is copied across.

It runs entirely on Atlassian's Forge platform, so no ticket data leaves your site. Queue Tidy is free while in beta.

Install the free beta

Questions