FAQ

What does this app actually do?

It reassigns the content a deactivated user owns — issue assignee and reporter, filters, component leads, and project leads — to an active teammate in one reviewed flow, and exports a closure-evidence CSV of what changed. The value is doing it in one pass and producing a record, rather than working through several separate admin screens with nothing to show afterwards.

Can Jira do this without the app?

Yes — native Jira can reassign these things, but across several separate admin screens, and with no export of what was changed. This app's job is the consolidation and the evidence, not a capability native lacks. We don't claim Jira “can't” reassign content.

Does it reassign a departed user's private filters?

Yes. The app uses the Administer Jira permission to reach a departed user's private filters. If it doesn't hold that permission on your site, those filters are shown as unreachable rather than acted on.

Does it cover dashboards?

Not in this version — dashboards are out of scope. A dashboard owner can't be transferred in a way the app can reliably read back to produce an honest record on Jira Cloud today, so the app never reassigns or evidences a dashboard (the listing, security page, and evidence export all say so). They are shown at preview for completeness, marked out-of-scope.

Is it safe to run? Can I see what will change first?

Yes. Preview shows the full plan as a dry run — the preview writes nothing to Jira, and reassignment runs only after you confirm. Runs are safe to retry, and a binding permission check gates the run before any write.

Does the export make my organization compliant / pass an audit?

No. The export is a factual record of the actions this app performed, to support your offboarding paperwork. It is not a certification or guarantee of compliance, and it covers the content types listed, not everything a user may have owned.

What happens if some items fail?

Failed items are shown with a reason; the run reports completed with failures; and the headline “reassigned” count excludes them. Nothing is hidden behind a green result.

Where is my data stored? Does anything leave Atlassian?

Everything runs on Atlassian's infrastructure (Runs on Atlassian). The app stores only account identifiers, item references, outcomes, and timestamps in Atlassian-hosted storage, and sends nothing to any external service. See Security & data handling.

How long is data kept? Can I delete it?

Per-change records carry a 90-day retention and age out automatically. You can also erase a run's records on demand after exporting, and the app's storage is purged when the app is uninstalled.

How much does it cost?

It's free for sites with up to 10 Atlassian users. For sites with more than 10 users, billing is per user from the first user — a site with 11 users is billed for all 11, not for one. There's a 30-day free trial, and billing is handled by Atlassian. See the listing's Pricing tab for the current rate.

Can I undo a reassignment?

There's no one-click “undo,” but every change is recorded in the evidence (from/to/when), so you can see exactly what moved and reassign it again if needed. Preview first to avoid surprises.

Does it run on a schedule or in the background by itself?

No reassignment ever runs on a schedule — the app only reassigns content when an admin runs it, and there's no real-time obligation, so it's safe to leave installed and use occasionally. (It does run one small background job: a weekly Personal Data Reporting cycle that reports the account identifiers it stores to Atlassian, so account closures can be propagated back and the corresponding data erased — a privacy-compliance requirement for any app that stores account IDs. That job performs no reassignment and touches no issue content. See Security & data handling.)