Draft. This app is not yet available.

MergeSafe Terms of Use

MergeSafe is licensed under Atlassian's standard Marketplace end-user agreement (Bonterms), shown on the Marketplace listing and install screen, together with the Provider-Specific Terms below.

Provider-Specific Terms for MergeSafe – Merge & Undo Duplicate Tickets for JSM Provider: YuvGev, Israel. Contact: [email protected]. Last updated: October 21, 2026.

1. Service description. MergeSafe merges one source ticket into one target ticket on your Jira Cloud site after a mandatory preview. It copies up to 100 comments as internal comments (each with an "Originally by" header), the source description as one internal comment, and up to 30 attachments under the project's size cap (larger files get an internal note pointing to the source); adds the source requester and participants to the target on Jira Service Management projects (up to 50, where the App is allowed to manage participants); adds a "duplicates" link and, if enabled, other links, watchers and labels; and transitions the source to a closing status with one "merged into" note (internal unless the project makes it public). The source ticket is never deleted. The documented limits are part of the service description, not defects, including: copies show the App as author; merges run as background jobs and aren't instant; duplicate suggestions never merge automatically; and Jira may send notifications for public comments and transitions.
2. Undo. Undo is available for 30 days after each merge. It deletes the internal comments and the attachments the merge created and removes only the participants, watchers, labels and links it added. Public comments stay in place, and an internal "merge undone" note is added to both tickets. The source is moved back to its previous status if a workflow transition exists; otherwise undo reports it for manual reopening. Notifications Jira already sent can't be recalled. Merges cleared with Clear history can't be undone.
3. No warranty of completeness. Jira permissions, issue security, workflows and rate limits apply. We don't warrant that every item will be copied or that every merge can be fully undone.
4. Customer responsibilities. Review the preview before confirming; choose who may merge and the closure settings; keep your own Jira backups.
5. Data. The App stores only settings, snapshots (summary, description up to 8,000 characters, status, participants, watchers and labels; no attachments), undo plans (kept 30 days) and audit records (kept 90 days) in Atlassian Forge hosted storage and sends nothing outside Atlassian. Clear history deletes the audit log and finished or expired undo plans; snapshots for merges still within the 30-day undo window are kept and auto-delete when the window ends. Our Privacy Policy applies.
6. License. Merge and undo need an active subscription; with an inactive license only the preview works.
7. Support. As described at yuvgev.com/apps/mergesafe/support/. No resolution time is guaranteed.
8. Liability cap. Our liability is limited to the fullest extent permitted by law.
9. Governing law. Laws of the State of Israel; courts of Tel Aviv-Jaffa exclusive.
10. Fees and refunds. Handled by Atlassian under the Marketplace terms.