How to merge duplicate requests in Jira Service Management

By Jake Marsh · Updated

To merge duplicate requests in Jira Service Management, open the service project, click Merge duplicates in the sidebar, pick a queue and click Find duplicate requests. Mergewell groups requests that look like the same problem and suggests the one to keep. Click Review merge, check the preview and click Merge. Each duplicate's customer becomes a request participant on the kept request, gets a public reply saying where updates continue, and the duplicate closes as Duplicate.

Why customers go quiet after a plain duplicate link

Jira Service Management sends updates to the reporter and request participants of a request. When an agent links two requests as duplicates and resolves one, the customer on the resolved request only sees it closed. Later replies on the kept request never reach them. Mergewell adds that customer to the kept request, which is the step a link alone doesn't do.

Steps

  1. Open your service project and click Merge duplicates in the left sidebar.
  2. Pick a queue in the Queue menu, for example "All open" or your triage queue.
  3. Click Find duplicate requests. Mergewell compares the summaries of up to 300 requests in that queue and shows groups such as "Similar summaries from the same reporter". The oldest open request in each group is marked Keep.
  4. Click Review merge on a group. The kept request and its duplicates are filled in; change the key in Keep (target) if you'd rather keep a different one.
  5. Check the switches. For service requests the ones that matter most are Keep people informed (reporter and request participants), Tell JSM customers where updates continue and Keep public replies public (JSM).
  6. Click Preview, read the warnings, then Merge.

To review older merges from the same page, click Merge history.

What each customer sees

  • On the duplicate: a public reply reading "Thanks for getting in touch. We are handling this together with a matching request, HELP-12, and you have been added to it, so you will get every update there. You do not need to do anything." Then the request closes. The reply is only posted when the customer was added to the kept request.
  • On the kept request: they're now a request participant, so they get its replies like the original reporter does.
  • What they don't see: another customer's messages. Copied public replies become internal notes on the kept request by default.

Turn on Keep public replies public (JSM) only when all the duplicates came from the same customer, such as one person who emailed and also filled in the portal form.

Cases the preview warns about

SituationWhat Mergewell does
The duplicate's customer isn't a customer of the kept request's service projectJira refuses to add them; the step counts them and adds everyone else
A copy step fails for one duplicateThat duplicate stays open and its customer isn't told, until you click Retry failed steps
The kept request is in a software projectCopied internal notes become visible to anyone who can see it, and the preview says so
SLAs on the duplicateSLA clocks react to the close, and to the reopen if you undo, as your SLA settings define

An outage example

Twelve "Email not syncing" requests come in within an hour. Pick the triage queue and click Find duplicate requests; they show up as one group. Keep the first one, choose Copy as one combined comment per duplicate so watchers of the kept request get one email per duplicate rather than one per comment, and merge. All twelve customers are now on one request, so one public reply when the fix lands reaches every one of them.

What it costs

Mergewell costs $5 a month for up to 10 users ($50 a year) and $1.04 per user a month from 11 users, with lower rates for larger sites, billed by Atlassian after a 30-day free trial. See the Mergewell page to install it.

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 Service Management have a merge feature?

Not as of November 2026. Atlassian's request for one, JSDCLOUD-4685, is marked Future Consideration. JSM can link and resolve requests, but it doesn't move comments or customers.

Can agents merge from the request itself instead of the queue?

Yes. On any request, the "..." menu has Merge duplicates, which works the same way for one request at a time.

Do the merged requests count against our SLAs?

Closing and reopening are ordinary transitions, so your SLA goals respond to them as configured. Undo doesn't rewrite SLA history.

Can I stop some agents from merging?

Yes. A Jira admin can limit merging to chosen groups under Who may merge on Jira settings > Apps > Mergewell.


More Mergewell guides


More Jira guides