Draft. This app is not yet available.

LabelSafe Terms of Use

LabelSafe 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 LabelSafe – Rename, Merge & Undo Labels for Jira Provider: YuvGev, Israel. Contact: [email protected]. Last updated: October 21, 2026.

1. Service description. LabelSafe lists Jira Cloud labels with approximate counts, finds near-duplicates, and renames, merges or deletes labels by editing each matching issue in a background job, with a preview, an audit list and undo. Jira has no rename-label API, so every change is an issue edit. The documented limits are part of the service description, not defects, including: approximate and case-insensitive counts; a preview that is a sample; jobs pausing at about 5,000 updated or 50,000 examined issues until resumed; issues the App can't edit being skipped; watchers possibly being notified when Jira ignores notifyUsers=false; undo restoring only the labels the job added or removed (not a full copy of the field); and history kept for the newest 30 jobs only.
2. No warranty of completeness. Jira search is not read-after-write consistent and rate limits apply. We don't warrant that every matching issue will be edited or that every edit can be undone.
3. Customer responsibilities. Review the preview before confirming; decide whether project admins may run cleanups; keep your own Jira backups.
4. Data. The App stores only settings and job/audit/undo records in Atlassian Forge hosted storage and sends nothing outside Atlassian. Our Privacy Policy applies.
5. Support. As described at yuvgev.com/apps/labelsafe/support/. No resolution time is guaranteed.
6. Liability cap. Our liability is limited to the fullest extent permitted by law.
7. Governing law. Laws of the State of Israel; courts of Tel Aviv-Jaffa exclusive.
8. Fees and refunds. Handled by Atlassian under the Marketplace terms.