Version 1.2.0. Commercial publication on Atlassian Marketplace is in progress. This guide describes the candidate app.
Set up a review
- A Jira Cloud administrator installs the app and grants its permissions.
- Open Jira settings → Apps → Leaver Guard. Jira administration and user search permissions are required.
- Choose up to 20 projects. An empty selection uses projects accessible to the app.
- Optionally add up to 20 people as planned departures. This does not deactivate or delete their accounts.
- Decide whether to include visible site-wide filters and dashboards. Their scope is not limited to the selected projects.
- Save the settings, start a scan, and review the people and items found.
What the app reviews
Leaver Guard reviews assigned open issues, project leads, component leads, accessible filter owners, and accessible dashboard owners. It identifies inactive accounts and people listed as planned departures. Private or inaccessible resources may be absent.
Priority combines account status with factors such as leadership, overdue work, or sharing. It helps administrators review work; it is not an employment assessment or advice to deactivate an account.
Prepare and confirm a handover
- Open a person's items and select an active successor for each resource.
- Create a preview and check the previous owner, successor, and scope.
- Confirm. The app reads the resource again and validates conditions before requesting the change in Jira.
- Check the history. A result is confirmed when a later read shows the successor as owner.
- For filters and dashboards, ask the successor to verify access to the content and gadgets they need.
The successor must be active and different from the previous owner. Issue, project, and component assignments require the relevant Jira permissions. A filter or dashboard may need additional visibility and permission changes in Jira.
If a change or interruption occurs
An edit after preview, revoked access, or a different owner may block the handover. Check the current state and create another preview. Jira may reject a dashboard with a conflicting name for the successor; the app does not rename it automatically. Recovery reads Jira state without automatically repeating an uncertain write. History distinguishes verification at transfer time from the owner observed later. There is no automatic reversal; prepare a new authorized handover to return ownership.
Scans, reports, and limits
Batches contain 1 to 500 items. Continue in stages or enable automatic continuation. Cancelling a scan preserves the last completed report. Weekly tracking creates reports; it never transfers responsibilities on its own. The CSV export contains records from the accessible history page, not a complete site export. Forge and Jira limits, permissions, and network failures can delay operations or produce partial reports.
License and support
An active or trial license is required for new scans, configuration changes, and handovers. Available reports and history remain accessible after the license becomes inactive, subject to their retention period. Contact support for help; see the data and retention policy.