Scanning and previewing

This covers steps 3–4: finding what the departed user owns, and reviewing the full plan as a dry run before anything is written.

Step 3 — scan (find what they own)

Select the departed user (step 1) and a validated target (step 2), then select Start scan. The app works through the content types listed — issue assignee and reporter, filters, component leads, and project leads — and builds an inventory of what the departed user currently owns.

• It's resumable. A large scan runs in the background and continues from where it left off if it's interrupted, so it doesn't have to start over.
• Reachable vs. unreachable. Each item is marked reachable (the app can read and act on it) or unreachable (for example, content the app can't read on your configuration). Unreachable items are shown, never silently dropped — this is the completeness guard, so the inventory and later evidence stay honest about what was and wasn't in scope.

Step 4 — preview (a dry run)

Open the Preview. This shows the full plan — every item that would be reassigned, from the departed user to your chosen target — without writing anything.

• The preview opens with a Dry-run notice: this preview writes nothing to Jira — it records the planned changes so you can review them before confirming. At this point nothing in Jira has changed.
• It lists the planned changes in a table — each item with its from/to owners and a status (Will reassign, Unreachable, or Out of scope) — along with any warnings to check before you continue.
• Reassignment writes happen only after you confirm in the next step.

Use Preview freely to check the plan before committing. Because it writes nothing, you can run it as many times as you like — a good way to sanity-check the target and the scope before the real run.

What you'll see: a planned-changes table with rows like Filter “Team triage” — owner → your chosen target, status “Will reassign”, with a planned-change count and any unreachable items shown below the plan — never reassigned. If something looks wrong (the wrong target, an unexpected item), stop here — nothing has changed yet.

Next: Confirming and running.