Offboard a Jira user without losing their filters and dashboards

The problem

When an account is deactivated first, the filters and dashboards it owned become orphaned, and nobody has a list of what mattered to the team. Permission grants made to the person directly survive every group review. And deleting the account is rarely what was actually wanted.

Step by step

1. Reassign ownership. Preview everything she owns. Every filter and dashboard is listed with its query, shares, favourites and last use, so you decide per object whether the team inherits it. Do this first, while you still know what mattered to her team.
2. Permission audit. Search for grants held by her as a named person. Group reviews cannot see these, and they survive every other offboarding step.
3. Revoke access. Remove her from the groups that grant access. Groups synced from your identity provider are rejected by Jira and reported as such; remove her there instead.
4. Orphaned objects. Run it a week later. Anything missed shows up here once her account is deactivated.

What to watch out for

Deleting the account is an organization-level action in admin.atlassian.com, outside Jira and outside any app. Revoking group access is the reversible equivalent, and usually what was actually wanted.