The closure-evidence export and retention

This covers step 7 — exporting the record of what changed — and how long the app keeps that data.

Step 7 — export the closure-evidence record

After a run reaches a terminal state, generate the closure-evidence CSV (select Generate evidence (CSV)). For each item the run touched, the record shows:

• the item and its type (issue assignee/reporter, filter, component lead, project lead),
• from whom (the departed user) and to whom (the target),
• when the change was attempted, and
• which admin ran it.

The CSV is presented as a copy-ready block you can copy out and save (the app's admin page surfaces it in-product). Each row reflects the actual final state, re-read after the write — the record is built from what the app confirmed happened, not from an assumption that a write succeeded.

How the record stays honest

• Mixed outcomes are shown in full. Items that succeeded, items that were already at the target (a no-op), and items that failed all appear. The headline “reassigned” count excludes the no-ops, so it reflects real changes only. Failed rows are shown plainly with their reason — never dropped.
• A completeness note. The record states that it covers the content types listed, not everything the user may have owned, and names what's out of scope (for example, dashboards and automation-rule actors).
• An artifact disclaimer. The record describes itself as a factual record of actions performed by this app; not a certification or guarantee of compliance. It is there to support your offboarding paperwork, not to make a compliance claim on your behalf.

A PDF export and an in-app file download are not part of this version (the admin page provides a copy-ready CSV). You can paste the CSV into a spreadsheet or your offboarding ticket.

Retention and erasing data

• Automatic retention. The per-change records that make up the evidence carry a 90-day retention. After that window they age out automatically.
• Erase on demand. Once you've saved the evidence you need, you can erase a run's records from the app immediately — useful if you'd rather not keep the data around.
• On uninstall. When the app is removed, it makes a best-effort pass to erase its run records, and Atlassian additionally purges all of the app's hosted storage when an app is uninstalled.

The app stores only account identifiers, item references, outcomes, and timestamps — display names are re-fetched only at export time and are not stored. See Security & data handling.