Jira · Inactive-User Hygiene

Find inactive Jira users and reclaim their licenses

Find idle and never-active Jira accounts from real Jira activity, and export a license-reclaim worklist as CSV.

Try it free on the Atlassian Marketplace Documentation

Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.

The gap

You pay per user, you suspect a chunk of those seats are dormant, and no screen in the product answers the plain question "who has not touched anything in 90 days?" Jira shows you who exists, not who is working.

What it does

Derives each user's last activity from Jira issue history (assignee or reporter).
Flags idle (beyond a threshold you set, default 90 days) and never-active accounts.
Estimates reclaimable seats: active accounts safe to review for removal.
Filters and sorts the worklist; highlights newly-idle users since the last scan.
One-click, audit-ready CSV export of the full worklist.
Unknown is never inactive: a failed lookup is marked unresolved and never flagged idle.

Users ranked by days idle, with reclaimable-seat counts at a glance.

The reclaim worklist: idle and never-active accounts with suggested review actions.

The daily scan derives last activity per user and never flags an unresolved lookup.

60-second walkthrough

Honest about its limits

It measures Jira activity, not org-wide login. The org admin API is not reachable by a tenant app, and Jira activity is the right signal for reclaiming Jira seats specifically. The report says so on its face.
Removing a user from product-access groups strips access but does not free the license seat. Only deactivating the account in admin.atlassian.com does that.
The one write path, honestly scoped: An opt-in, admin-confirmed removal takes reviewed idle users out of their product-access groups, always from a preview you approve. Groups that look IdP-synced are skipped, because your identity provider would re-add them.

Security & permissions

Built on Atlassian Forge: the app runs on Atlassian's own serverless platform inside your tenant, stores its data in Forge storage, and makes no external network calls. Every scope it requests, and why:

read:jira-user	enumerating the roster
read:jira-work	deriving last activity from issue history
storage:app	the cached worklist, in your tenant

FAQ

Does any data leave my instance?

No. The app runs on Atlassian Forge inside your own tenant with zero external egress, which makes it eligible for Atlassian's "Runs on Atlassian" trust marker.

How is it billed?

Through the Atlassian Marketplace, on your existing Atlassian bill, priced per user like any Cloud app. The listing has a free evaluation and the exact calculator for your tier.

Where do I get support?

Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.

Install Inactive-User Hygiene in about a minute.

Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.

Try it free