Merge Issues in Jira: How to Combine Duplicate Work Items

Jira can link duplicates but can’t merge them. See what a full merge moves, how to do it step by step, and how Service Pack for Agents handles it.

Krzysztof Skoropada Feb 22, 2022

Merging issues in Jira means combining two or more duplicate work items into one, so comments, attachments, and field values end up in a single place. Jira Cloud has no native merge: you can link a work item as a duplicate and close it, but its data stays where it was. To merge, you need a Marketplace app.

Duplicates clutter queues and boards, slow teams down, and skew reports. Below you’ll find what a proper merge moves, how to do it, and how the Merge Issues feature in Service Pack for Agents works.

Why Duplicate Work Items Are a Problem

Duplicates often appear when multiple users report the same bug or incident, or when requests are created from different channels like email, portal, or integrations. Instead of one clear source of truth, teams end up managing several tickets for the same problem.

This leads to:

extra work for agents and developers,
inconsistent communication with customers,
fragmented comments and attachments,
inaccurate metrics and reports.

Native Jira Options

Out of the box, Jira allows you to:

link work items with the “Duplicate” link type,
close the duplicate with the Duplicate resolution,
copy comments or attachments by hand.

While these options help with visibility, they don’t actually solve the problem. Information is still spread across multiple issues, and teams must remember to update more than one ticket.

Merging is still an open feature request for Jira Cloud (JSDCLOUD-4685).

What Merging Work Items Means

Merging issues means combining multiple Jira issues into one. A proper merge usually includes:

moving comments to a single issue,
copying or moving attachments,
preserving issue links,
closing or resolving duplicates automatically.

This approach creates one authoritative issue while keeping historical context.

Data	Linked as duplicate (native)	Merged with Service Pack for Agents
Comments	Stay on the duplicate	Moved to the target, including public and internal JSM comments
Attachments	Stay on the duplicate	Moved to the target
Watchers, labels, votes	Stay on the duplicate	Moved to the target
Request participants, organizations	Stay on the duplicate	Moved to the target
Custom fields	Stay on the duplicate	Basic and advanced custom fields supported
Comments added later	Land on the duplicate	Can sync to the target automatically
Duplicate’s status	Changed by hand	Changed in the merge dialog

How to Merge Issues in Jira Step by Step

Because Jira Cloud does not support a true merge natively, many teams rely on Marketplace apps. These apps automate the process and reduce manual work.

A typical workflow looks like this:

Identify duplicate issues.
Select a primary issue.
Merge secondary issues into the primary one.
Automatically close duplicates and notify stakeholders.

In Service Pack for Agents, open the Actions menu on the source work item and select Merge. You can choose several source and target work items, or pick them with a filter, then select the fields to merge and what happens after the merge. Presets save a field selection you use often.

When Merging Makes Sense

Issue merging is especially useful in:

Jira Service Management spaces (formerly projects) with high request volume,
incident and problem management,
bug tracking in Jira Software,
support teams handling customer‑reported duplicates.

Summary

Jira links duplicates but leaves their data split across work items.

A merge moves comments, attachments, and fields into one work item and closes the rest. If your team handles duplicates every week, Service Pack for Agents merges them from the work item, by rule, or through a Rovo agent.