Skip to:

Marketplace

Leaver Cleanup & Owner Reassignment for Jira

works with Jira Cloud

OVERALL RATINGS

INSTALLS

1

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appReassign a departed user's issues, filters, components and project leads - and export closure evidence

hero

Reassign a leaver's content in one flow

Find the issues, filters, component leads and project leads a departed user owns, pick an active teammate, and bulk-reassign them in one reviewed pass instead of clicking through separate admin screens.

Export a closure-evidence record

Every run produces a CSV of exactly what changed - each item, from whom, to whom, when, and by which admin - to support your offboarding paperwork. A factual record of the app's actions, not a compliance guarantee.

Preview every change before it is written

Nothing is written until you confirm. Preview the full plan as a dry run, reassign only to a validated active target, retry safely if interrupted, and see any failures plainly, never hidden behind a green check.

Supporting media

More details

Deactivating a user doesn't move what they owned. Their issues, filters, component leads and project-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.

This app does it as one reviewable flow: pick the departed user, see what they own across the supported content types, choose an active teammate, preview every change, then bulk-reassign in a single pass. Every run is previewed before anything is written, is safe to retry, and records each change.

It then exports a closure-evidence CSV - what was reassigned, from whom, to whom, when, and by which admin - to support your offboarding paperwork. The record is a factual log of the actions this app performed; it is not a certification or guarantee of compliance, and it covers the content types listed, not everything the user may have owned (for example, dashboards and automation-rule actors are out of scope).

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Leaver Cleanup & Owner Reassignment for Jira integrates with your Atlassian app

Version information

Version 3.5.0for Jira Cloud

Release date
Jun 12th 2026
Summary
First release: reassign a departed user's content and export closure evidence.
Details

Version 1.0 - the first release. Find and bulk-reassign the content a deactivated or departed user owns across Jira, in one reviewed flow: issue assignee, issue reporter, filters, component leads, and project leads. Every run is previewed as a dry run before anything is written, reassigns only to a validated active target, is safe to retry if interrupted, and shows any failures plainly. After a run, export a closure-evidence CSV of what changed: each item, from whom, to whom, when, and by which admin. Not included in this version: dashboards, project-role memberships, automation-rule actors, and watchers/mentions. The record covers the content types listed, not everything a user may have owned; it is a factual record of the app's actions, not a certification or guarantee of compliance.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow