Skip to:

Marketplace

Merge Requests for Jira Service Management

works with Jira Cloud

INSTALLS

No installs yet

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appMerge duplicate requests into one. Comments, files, people and links are copied to the main request, and the duplicate is closed

watch Merge Requests for Jira Service Management video

Merge from the request

Pick the duplicates, see what will be copied, and confirm. Each copied comment shows who wrote it, when, and whether it was public. Public comments are copied as internal unless your Jira admin chooses otherwise.

People, files and links too

Files, request participants, organizations, watchers and links are copied as well. Anything left out, such as a file over your size limit, is listed with the reason, so you can add it by hand.

A clear record

Every merge is logged before anything changes. If a step fails, the merge stops, says which step, and leaves that duplicate open. Try again carries on from there. Download the log as CSV.

More details

When customers raise the same problem twice, agents answer in two places. Merge Requests puts it all in one request.

An agent opens Merge requests from the ••• menu on a request, picks up to 10 duplicates and confirms the preview. Then each duplicate is linked as a Duplicate of the main request, both get an internal note, and the duplicate moves to the done status your Jira admin chose. A resolution is set only if one was chosen and the Resolution field is on that transition’s screen.

Only agents of the service project can merge, with the permissions the merge needs on each request. The app makes the changes; the copied comments and both notes name the agent.

Jira emails customers when a public comment is added, and its API cannot stop that. So by default public comments are copied as internal. A Jira admin can keep them public. Comments limited to a group or role the app is not in are listed as left out.

Runs on Atlassian. No comment text, file content or email addresses are stored.

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Merge Requests for Jira Service Management integrates with your Atlassian app

Version information

Version 3.0.0•for Jira Cloud

Release date
Nov 17th 2026
Summary
First release: merge duplicate requests, with comments, files and people
Details

Agents merge duplicate requests from the request’s ••• menu. Comments, files, participants, organizations, watchers and links are copied to the main request, the duplicate is linked and closed, and every merge is logged.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow