Skip to content
Wayflare

Documentation — Leaver Cleanup & Owner Reassignment for Jira

Last updated · 12 June, 2026

What this app does

When someone leaves your organization and their Jira account is deactivated, the things they owned don't move on their own — their issues, filters, and lead roles keep pointing at an inactive account. Tidying that up natively means working through several separate admin screens, with no record to show for it afterwards.

This app does it as one reviewed flow: pick the departed user, see what they own across the supported content types, choose an active teammate, preview every change, bulk-reassign in a single pass, and export a closure-evidence record (a CSV) of exactly what changed. 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.

Who it's for

Jira Cloud administrators (you need the Administer Jira permission) who handle offboarding and want to reassign a departed user's owned content in one place, with an exportable record.

What's covered (the content types listed)

  • Issues — assignee and reporter
  • Filters — owner (including a departed user's private filters)
  • Components — component lead
  • Projects — project lead

What's not covered (out of scope in this version — named honestly)

So “closure evidence” is never read as “everything,” this version does not cover: dashboards (owner transfer is a current limitation — see Troubleshooting); automation-rule actors (Jira natively transfers these via Transfer automation rules); project-role memberships; board administration; group memberships; watchers and mentions (participation, not ownership); comment and worklog authorship (not reassignable in Jira); and JSM customer-portal content. The evidence record covers the content types listed, not everything a user may have owned.

Installing

  1. From the Atlassian Marketplace listing, choose Get it now / Try it free and install it on your Jira Cloud site (you must be a site admin).
  2. Review and accept the permission scopes on the consent screen (see Security & data handling for why each is needed).
  3. Open it from Jira → Settings (gear) → Apps → Leaver Cleanup & Owner Reassignment for Jira (it appears in the admin Apps section).

The app runs entirely on Atlassian's infrastructure (Runs on Atlassian) — it stores its data in Atlassian-hosted storage and sends nothing to any external service.

The one flow (seven steps)

  1. Leaver — review the deactivated users the app finds and choose the departed user.
  2. Target — pick an active teammate to receive the content; the app validates them automatically.
  3. Scan — find what the departed user owns across the content types listed.
  4. Preview — review the full plan as a dry run; nothing is written yet.
  5. Confirm — a binding permission check runs, then you confirm.
  6. Run — the reassignment runs in the background; it's safe to retry if interrupted.
  7. Evidence — export the closure-evidence CSV of what changed.

First run

Start with Detecting the departed user and validating the target. A good first run is to scan a single departed user and use Preview to see exactly what would change — Preview never writes anything, so you can explore safely before confirming.

Pricing (at a glance)

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