How-to
How to find inactive Jira users
Use two checks. Atlassian Administration (admin.atlassian.com) shows when each user was last active, which catches people who stopped logging in. JQL catches the rest: people who still log in but haven't created, edited or commented on anything in months.
Step 1: check last active dates
Open the user list in Atlassian Administration. It shows a last active date per person, and you can export the list as a CSV file. Sort by that date and mark anyone past your cut-off, say 90 days. Column names differ a little between admin experiences, so look for last active or last seen.
Step 2: check who does real work
In Jira, open the work item search and switch to JQL. For each person, run:
issuekey in updatedBy(<user>, "-90d")updatedBy() finds items the person created, edited or commented on in that window. Then try:
assignee = <user> AND updated >= -90dJira Cloud identifies people by account ID. You'll find it at the end of their profile URL. No results from either query means no work in that period.
Where it gets slow
It's two searches per person. At 40 users that's an afternoon. At 400 it's days of copy and paste, and you'll want to redo it before every renewal. Neither check is perfect on its own either. Someone who reads Jira daily and never edits looks idle to JQL, which is why the login date matters.
Run the JQL part for everyone at once
Access & License Audit runs these activity checks for every seat holder in one scan, over 30 to 365 days. The People tab lists who's inactive with their products and groups, and copies to CSV. It can't see logins because Jira doesn't share them with apps, so pair it with the export from step 1.