1. What the app does (and does not do)
Ticket Merge adds the action Merge into another ticket to the "..." menu of a Jira issue. It copies the comments, attachments and links of the duplicate to the main ticket, links the two as duplicates and closes the duplicate. It does not delete any ticket. Undo is available for 30 days. Jira has its own merge action (March 2026) for Jira Software and Jira Business projects; this app is for tickets, including service requests, where you want a preview, a log and undo.
2. Install and permissions
Install from the Atlassian Marketplace as a site admin. The app asks for: read and write Jira work (tickets, comments, attachments, links, status changes); read and write service desk requests (participants); app storage (the merge log). It makes no calls outside Atlassian. See the privacy policy. Licence: free for sites with up to 10 users; above that, the price shown in the Marketplace. If the licence is not active, "Merge" is blocked; preview and undo still work.
3. Your first merge
- Open the duplicate ticket. Click "..." and choose Merge into another ticket.
- Enter the key of the main ticket (for example SUP-12) and click Preview.
- Check the numbers (comments, attachments, links, customers), the warnings and the note that the duplicate will be closed.
- Click Merge. The dialog shows the status. You can close it; open it again later to see the result and the Undo button. You need these permissions: on the duplicate: browse, transition, comment; on the main ticket: browse, comment, create attachments, link issues.
4. What is copied and what is not
| Item | Behavior |
|---|---|
| Comments | Copied as new comments by the app, with a header line (source key, author, date, internal/public). The original stays. |
| Attachments | Copied (download and upload). Files over 10 MB are skipped and listed as a warning. A file with the same name and size already on the main ticket is not copied again. |
| Links | Links to other tickets are copied to the main ticket. A link between the two tickets is not copied. |
| Customers | For service requests: the reporter and participants of the duplicate are added to the main ticket (tested on a Jira Service Management site). |
| Not copied | Ticket fields (title, description, priority, custom fields), worklogs, watchers, history, comment reactions and edit history. |
| After copying, the app adds a note on the main ticket, links the tickets as "Duplicate", and closes the duplicate with the first available transition to a "done" status. If your workflow needs a mandatory field to close, that step can fail; the app shows that it needs help. |
5. Internal and public comments
The app copies the internal or public flag and never makes an internal comment public. Tested on a Jira Service Management site: an internal comment stays internal on the main ticket and is not visible in the customer portal; public comments stay public.
6. What customers see and the email limit
Copied comments and notes are created in the tickets and can trigger the notifications of your Jira Service Management project . An email that a customer has already received cannot be taken back. Undo restores tickets, not inboxes. In the customer note the app tells the customer where updates continue.
7. History and Undo
The dialog has a History tab: every merge with time, person, tickets, result and whether it was reverted. Before a merge, a comparison preview shows both tickets side by side. To undo, click Undo in the history, or open the closed duplicate, open the dialog and click Undo. Available for 30 days. It deletes the comments, attachments, links, note and participants the app created and reopens the duplicate. If someone changed the status since, the status is not overwritten and the app reports it. After 30 days the log is removed and undo is no longer possible.
8. "Partly done" and "needs help"
If a step fails, the app retries automatically (after 60 seconds, up to 3 attempts per step). The duplicate is closed only after all copy steps worked. If a step keeps failing, the status shows "Partly done"; use Undo or ask a site admin. Starting a second merge of the same ticket while one is running is blocked, so double clicks do not duplicate anything.
9. Who may merge and undo
Any agent who can open the action and has the permissions listed above may merge. Any agent with access to the app can undo any merge (no role model yet).
10. Data, privacy, retention, uninstall
Merge records (keys, IDs, status) stay 30 days in your site's Forge storage; no ticket texts. Nothing leaves Atlassian. Uninstalling removes the stored data . Copies in your tickets stay unless undone. Details: privacy policy.
11. Pricing, licence, limits, contact
Free up to 10 users; above that the Marketplace price per user and month. Known limits: sent emails not recallable; whether Undo can reopen a closed duplicate depends on your workflow (some workflows have no way back from the closing status, then the app tells you to change the status by hand); attachments over 10 MB skipped; the app does not merge fields; Atlassian may change its own merge function. Contact: see the support page.