Detecting the departed user and validating the target

This covers steps 1–2 of the flow: choosing the departed user, and validating the active teammate who will receive their content.

Step 1 — choose the departed user

1. When you open the app's admin page, it looks across your site for deactivated accounts automatically and shows each one with a rough indication of what it still owns. Use Re-check to refresh the list.
2. Pick the departed user you're offboarding and select Select.

Under Diagnostics at the bottom of the first screen, you can also select Check app permission status to see whether the app currently holds the Administer Jira permission it uses to reach a departed user's private filters. The app receives this permission from the Atlassian-managed add-on admin group when it is installed; it is a capability the app holds on your site, not a per-app toggle you set.

Why “deactivated”? The flow is built around a user whose account has been deactivated as part of offboarding. Reassigning the content of an active user is a different task and isn't the focus here.

Step 2 — validate the target

Before anything is scanned for reassignment, choose the active teammate who will become the new owner — search by name or email in the user picker, and the app validates them automatically when you pick. (If a user can't be found in the picker, you can enter their account ID manually and select Validate target.) The app checks that the target:

• is active (not deactivated),
• is a real, resolvable account, and
• is able to own each item type involved (you can optionally give a project key to verify the new owner can be assigned issues in that project).

If the target can't validly own an item, the app tells you up front rather than letting a reassignment silently orphan content to an unusable account. A deactivated or unresolvable target is rejected with a clear reason.

Tip: the target should be someone who will genuinely take over the work — a team lead or the departed user's manager is a common choice. You pick a single target for the run.

What happens to the data

Detecting users and validating the target only reads account information; nothing is written in these steps. The app stores account identifiers and item references (not display names — those are re-fetched only when you export). See Security & data handling.

Next: Scanning and previewing.