How many Jira seats are you paying for that nobody has touched in 90 days?

[#1]

You pay for Jira by the user, you suspect a chunk of those seats are dormant, and no screen in the product will tell you which ones. Jira shows you who exists, not who is actually working.

The question tends to land at the worst time: a renewal quote, a license true-up, or the moment finance asks why the Jira bill keeps climbing. It is also one of the most-requested gaps in the product. ID-8172 ("Bulk delete users") has sat open for years with around 671 votes, and before anyone can safely remove users, they need exactly this list first.

You can approximate it yourself: pull the user list, cross-reference last-active dates from the REST API, and flag anyone past your threshold. That works, until the script's author leaves or a security review asks whose token it runs on.

Disclosure: I work for Katabarwa Labs, and we build a small app for exactly this, so treat it as one option among whatever you evaluate.

Inactive-User Hygiene reads real Jira activity and flags the two things admins act on: idle-but-still-licensed accounts past a threshold you set, and never-active accounts that were provisioned and forgotten. It totals the reclaimable seats, exports the worklist as CSV for review, and offers an opt-in, preview-first removal of reviewed users from their product-access groups (always a dry run you approve, never automatic, and it skips IdP-synced groups your directory would just re-add). It runs entirely on Atlassian Forge inside your tenant, so nothing leaves your instance, and the report itself is read-only.

Listing, if it helps: Inactive-User Hygiene. If your license review needs something it does not surface yet, tell us and we will build it.