How to find duplicate issues in Jira
By Jake Marsh · Updated
To find duplicate issues in Jira, open Apps > Mergewell, stay on the Find duplicates tab, type a JQL search in Look for duplicates among and click Find duplicates. Mergewell compares the summaries of up to 300 work items from that search and lists groups of likely duplicates, each with a "% similar" score and a suggested work item to keep. Click Review merge on any group to merge it.
Why JQL alone doesn't find them
JQL matches words you already know. summary ~ "login" finds every work item with "login" in the summary, but not "can't sign in" or "Log-in page broken", and it can't tell you which results are about the same problem. You end up reading the whole list. Mergewell scores every pair in the search against each other, so similar summaries cluster even when the wording differs.
Steps
- Open Apps > Mergewell from Jira's top bar.
- Write the search in Look for duplicates among. The default is
created >= -30d AND statusCategory != Done ORDER BY created DESC. Narrow it to one project or one type to keep results focused. Need help with the syntax? Our free JQL query builder writes it from menus. - Click Find duplicates. The button reads Searching while Mergewell compares summaries.
- Read the groups. Each one lists its work items with status and score, and a reason: "Similar summaries" or "Similar summaries from the same reporter". The oldest open work item is marked Keep.
- Click Review merge on a group you agree with, then preview and merge, or leave it if they're only related.
How the matching works
- Summaries are compared by shared words and by three-letter fragments, so "password reset" and "passwords resetting" still match. Common words like "issue", "help", "urgent" and "please" are ignored, and numbers are kept, so error codes and order numbers count.
- Two work items from the same reporter created within 7 days get a higher score, since a person filing twice is the most common duplicate on a service desk.
- A group needs at least one open work item. Closed ones can appear in a group, but only open ones are suggested as duplicates to merge.
- The comparison runs inside the app on Atlassian's platform; nothing is sent to an outside service.
Searches that work well
| You want | Search |
|---|---|
| New bugs in one project | project = APP AND type = Bug AND created >= -14d |
| Everything still open in a service project | project = HELP AND statusCategory != Done |
| One component | project = APP AND component = Checkout AND statusCategory != Done |
| Requests from this week | project = HELP AND created >= startOfWeek() |
Searches over 300 results only compare the first 300, so put the most likely duplicates first with ORDER BY created DESC or a tighter filter.
Finding work items that were already merged
Every duplicate Mergewell closes carries an issue property you can search in Jira's own issue search. mergedInto = HELP-12 lists every work item merged into HELP-12, including ones merged months ago by someone else. Save it as a filter on the kept work item's project to see which requests were folded into it.
What it costs
Mergewell is $5 a month for up to 10 users or $50 a year, then $1.04 per user a month from 11 users, with lower rates for larger sites. Atlassian bills it and gives a 30-day free trial. Details are on 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
Does Jira detect duplicates automatically when an issue is created?
Mergewell doesn't flag duplicates as they're created. It finds them when you search, on the Find duplicates tab, in a service queue, or from a work item's Merge duplicates menu.
Why didn't two obvious duplicates show up?
Matching uses the summary only, not the description. Two work items with very different summaries won't group; merge them by key on the Merge by key tab instead.
Can I search across several projects at once?
Yes. Any JQL works, such as project in (APP, WEB). Groups can mix projects, and merges work across projects.
Is there a threshold I can change?
No. Groups form above a fixed similarity score. The score is shown on every work item, so you decide what to merge.