How to merge two Jira tickets into one
By Jake Marsh · Updated
To merge two Jira tickets, install Mergewell, open the ticket you want to keep and choose Merge duplicates from its "..." menu. Pick Merge duplicates into HELP-12 (keep HELP-12), tick the other ticket or type its key, click Next: choose what to copy, then Preview and Merge. Its comments, files, links, labels and watchers move to the ticket you kept, and the other one closes with the resolution Duplicate and a Duplicate link.
Before you start
- Jira Cloud, with Mergewell installed by a Jira admin from the Atlassian Marketplace.
- Permission to comment on, attach files to and link the ticket you keep, and to transition the one you close. Mergewell runs every step as you, so Jira's own permissions apply.
- Jira has no merge button of its own. Without an app, the closest you get is linking the two tickets as duplicates and closing one, which leaves its comments and watchers behind.
Steps
- Open the ticket you want to keep. Usually the older one, since it already has the history. Mergewell suggests the oldest open ticket when it groups duplicates for the same reason.
- Click "..." in the top right and choose Merge duplicates.
- Choose the direction. Merge duplicates into HELP-12 (keep HELP-12) keeps the ticket you're on. Merge HELP-12 into another work item asks for the key of the ticket to keep, and closes the one you're on.
- Pick the other ticket. Under Likely duplicates in this project, Mergewell lists up to 10 tickets created in the last 180 days with similar summaries, each with a "% similar" score. Tick the right one, or type its key in Other keys.
- Click Next: choose what to copy. The defaults copy the comments as one combined comment, the description, attachments, links, labels and watchers, keep the reporter informed, and close the duplicate.
- Click Preview. Read the row for the duplicate, the Check these first box if one appears, and the box listing what Undo cannot reverse. Click Change to go back and adjust.
- Click Merge and keep the window open until the steps finish. Most merges take seconds; large attachments take longer.
What ends up where
| The ticket you keep | The ticket you merge | |
|---|---|---|
| Comments | Copied in, with each original author and time | Stay where they are |
| Description | Added as an internal note | Unchanged |
| Files | Copied, up to the size limit (20 MB by default) | Stay where they are |
| Links and labels | Added | Unchanged |
| Watchers and reporter | Added as watchers, or as request participants on a service request | Unchanged |
| Status | Unchanged | Closed, resolution Duplicate |
| Trail | A note listing what was copied, and a Duplicate link | A "merged into" note and a Duplicate link |
Sub-tasks, child work items and field values such as priority or due date are not moved.
Choosing how comments come over
- Copy as one combined comment per duplicate posts a single comment holding the whole thread, so watchers get one email. Pick this for long threads.
- Copy one by one, each with an "Originally by" line keeps each comment separate, which reads better when the conversation matters line by line.
- Don't copy comments when the duplicate only said "same here".
Either way, mentions become plain text so nobody in the old thread is pinged again, and comments restricted to a group or role keep that restriction.
If you merged the wrong one
Open the merge (it stays on screen, or find it under Apps > Mergewell > History) and click Undo merge. For 24 hours by default it removes the copied comments, files, links, labels and watchers, removes the Duplicate link and reopens the closed ticket. Emails Jira already sent can't be unsent.
What it costs
Mergewell is $5 a month for up to 10 users, or $50 a year, and $1.04 per user a month from 11 users, with lower rates on larger sites. It's billed by Atlassian with a 30-day free trial. Install it from the Mergewell page.
Mergewell: Merge Duplicate Issues and Requests
Merge duplicate Jira issues and service requests into one. Preview every change, keep every customer informed, undo for 24 hours. From $5 a month for up to 10 users.
Questions
Can I merge more than two tickets at once?
Yes. Tick several suggestions or type several keys, up to 20 duplicates in one merge by default. Admins can raise the limit to 50.
Can I merge tickets from two different projects?
Yes. Type the other ticket's key by hand; the suggestions only cover the current project, but the merge works across projects.
Does the merged ticket get deleted?
No. It's closed and linked, with all of its own comments and files still on it.
Who sees the copied comments?
Anyone who can see the ticket you kept. The preview warns you when internal notes from a service request would land on a ticket in a software project.