Access and requirements
Offboarding Transfer Utility is a Jira administration page. A Jira administrator opens Jira settings, selects Apps, and then opens Offboarding Transfer Utility.
Jira administrator
The invoking user must have Jira's global administrator permission. The App verifies this permission for every user-invoked operation.
Licensed access
An active Atlassian Marketplace subscription or a valid trial is required to scan, transfer, view history, or delete history.
If the App displays License required, ask a site administrator to start a trial or activate the subscription, then refresh the page.
The three-step workflow
1. Select departing user
Search for and select the Jira user who is leaving. The App scans the supported Jira categories and presents the asset footprint for review.
2. Choose successor
Select the Jira user who should receive ownership or open-issue assignments. The successor must be different from the departing user.
3. Review and transfer
Review the departing user, successor, and category totals in the confirmation dialog. The App does not begin changes until the administrator confirms the transfer.
Result
The completion state reports successful and failed counts by category. Review any item-level errors before retrying or making manual Jira changes.
Supported Jira assets
The App scans and transfers the following categories when they are associated with the selected departing user:
- Filters: ownership of supported Jira filters.
- Dashboards: ownership of supported Jira dashboards.
- Project leads: the lead assigned to Jira projects.
- Component leads: the lead assigned to Jira project components.
- Open assigned issues: open Jira issues currently assigned to the departing user.
Jira applies its own permissions and product rules to every change. An individual item can fail even when other categories complete successfully.
Administrator-only transfer history
Transfer history is available only to licensed Jira administrators. The App stores one audit record for each completed transfer run in Atlassian Forge storage. A record identifies the administrator, departing user, successor, timestamp, category counts, outcomes, and bounded error details.
180-day retention: audit records expire automatically 180 days after creation. A Jira administrator can also delete all retained transfer history immediately from the App.
Asset details found during a scan are transient and are not retained as a separate inventory. For the complete data-handling description, read the Privacy Policy.
Review and transfer safety
The App cannot automatically undo a transfer. Confirm the selected users and asset totals carefully. A partial result means successful items may already have changed even when other items failed.
After a partial failure, review the reported category and error, then rescan the departing user before deciding whether a retry is appropriate.
Support
Need help with a scan or transfer?
Read the support policy for contact details, response targets, transfer-safety guidance, privacy requests, and security reports.