Supported by the people who built it.

A Remove decision changes nothing by itself. Remove the person's groups in Atlassian Administration, or use Seat Reclaim for Jira, which frees inactive users' seats after you confirm and can undo it.

Confluence activity is not counted, so a Confluence-only user who sits in a Jira group shows as no activity.

A user who only reads issues cannot be distinguished from one who never opens Jira. Jira Cloud does not expose login history to apps.

Jira doesn't label admin groups for apps, so any group whose name contains "admin" counts as one. Admin groups named differently show as ordinary groups; filter by group to review them.

If more than 20,000 issues were updated in the window, the activity sweep stops at the most recent 20,000. Every user is still checked individually, but Jira cannot search comments by author, so someone whose only activity was a comment on an older issue may show as inactive. The review says so when this happens.

The page and the evidence file cover up to 5,000 people. If your site has more group members than that, tell us before you start.

Jira Service Management portal-only customers and app accounts are left out, because they hold no seat and no group access.

Emails are hidden for users whose profile privacy settings don't share them with apps.