Merge duplicate tickets in Jira Service Management and Jira. Comments, attachments, watchers and request participants move to the ticket you keep. The duplicate is linked, closed as "Duplicate", and the customer is told where the conversation continues.
SUP-123) and click Check. You'll see the target and how many comments, attachments, watchers and participants will move.Every option can be switched off per merge. The admin page (Jira settings → Apps → TicketMerge for Jira) shows the last 100 merges with each step's result.
TicketMerge acts as the person merging, so Jira's normal permissions apply: you can only merge tickets you can see and edit, and only add watchers or participants you're allowed to add.
Yes. In Jira Software and business projects it merges comments, attachments, watchers, labels and links, and closes the duplicate. Participant and customer-note options appear for service projects.
The duplicate isn't deleted. Reopen it if needed. Copied comments and attachments stay on the kept ticket.
Only the merge history (ticket keys and step results) is kept, in Forge storage on Atlassian's infrastructure. See the privacy policy.
Email support@puzaricloud.in with your Jira site address. We reply within one business day (Monday–Friday, India time).