Status: pre-launch. IssueRescue is not yet available for installation or purchase via the Atlassian Marketplace. This page describes the terms that apply now, and the framework that will govern the Marketplace subscription once it launches. It will be updated when the Marketplace listing goes live and when the documents referenced below (IssueRescue Provider-Specific Terms, Data Processing Agreement) are published.

Terms of Use

Effective date: 13 September 2026

These Terms of Use ("Terms") govern use of IssueRescue for Jira ("IssueRescue", "the app"), a Forge app for Atlassian Jira Cloud provided by Stephen Hutchins ("we", "us"). By installing or using IssueRescue, the installing organization and its users agree to these Terms.

1. What IssueRescue does

IssueRescue captures a snapshot of a Jira issue's data while the issue exists, so that if the issue is later deleted, a Jira administrator can restore it as a new Jira issue populated from that snapshot. IssueRescue is a recovery aid, not a guarantee of exact or complete restoration:

A restored issue is always assigned a new Jira issue key/ID and a new creation date by Jira itself — the original key, ID, and creation date can never be reused or restored.
The full change history/audit log of the original issue is not preserved and cannot be restored.
Comment and worklog authorship cannot be reassigned via Jira's API — restored comments and worklogs are created under IssueRescue's own identity, with the original author and date preserved only as a text note, not as real Jira metadata.
Some fields may not be restorable depending on your Jira project's configuration at the time of restore; IssueRescue reports which fields it could not restore rather than guessing at their values.

See the product page for a fuller summary, and the Privacy Policy for what data is involved.

2. Eligibility and access

IssueRescue's admin page and its actions (viewing deleted issues/history, restoring an issue, permanently deleting a stored snapshot) are restricted to users who hold Jira's global "Administer Jira" permission on the installed site. The installing organization is responsible for who it grants that permission to, and for how those administrators use IssueRescue — including deciding when to restore or permanently delete a given item.

3. Your responsibilities

You are responsible for the data you and your organization put into Jira issues, comments, and worklogs, including any personal data about third parties.
You are responsible for reviewing a restored issue's content before relying on it, including checking for any fields IssueRescue reported it could not restore.
You are responsible for complying with applicable law (including data protection law) regarding the data your organization processes using IssueRescue.

4. Data handling

How IssueRescue collects, stores, retains, and lets you exercise rights over data is described in the Privacy Policy, which forms part of these Terms. A Data Processing Agreement (DPA) covering our processing of personal data on your organization's behalf will be made available to customers where applicable, ahead of any paid Marketplace launch. It is not yet published — this page will link to it once it is.

5. Availability and changes

Once available via the Atlassian Marketplace, IssueRescue will be provided as-is, and its availability will depend on Atlassian's Forge platform and Jira Cloud REST APIs remaining available. We may update, change, or discontinue features of the app, and may update these Terms, from time to time; when we do, the effective date at the top of this page will be updated accordingly.

6. Marketplace subscription terms

Once IssueRescue is offered as a listing through the Atlassian Marketplace, use and purchase of that Marketplace subscription — including warranty, liability, and related transactional terms — will be governed by Atlassian's standard customizable End User Agreement (EUA) for Marketplace transactions, in the form Atlassian presents to you at the time of purchase or installation. Any additional IssueRescue-specific terms we publish ("Provider-Specific Terms") will supplement, and do not replace, that End User Agreement. We do not reproduce Atlassian's End User Agreement text on this page and do not restate or invent its clauses here — the version Atlassian presents to you at the time governs your transaction, not this summary.

7. Termination / uninstalling

You may uninstall IssueRescue from your Jira site at any time via Atlassian's own app management tools. What happens to already-stored data after uninstalling is governed by Atlassian's own platform-level retention policy for Forge apps — see the Privacy Policy — not by IssueRescue itself.

8. Governing law

The governing law and jurisdiction for the Atlassian standard End User Agreement covering your Marketplace subscription is as set out in that agreement. For any IssueRescue Provider-Specific Terms we publish to supplement it, the governing law is the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction over any dispute arising specifically from those Provider-Specific Terms.

9. Contact

Questions about these Terms: support@issuerescue.co.uk