TELCOMA Global / License Audit for Jira / Documentation
Find the Jira seats nobody is using.
License Audit lists the licensed users on your Jira Cloud site who have done nothing in Jira for a period you choose, so you can decide which seats to reclaim. It is read-only: it never deactivates anyone and never changes anything on your site.
Install
Three steps, all inside Jira.
Find the app
In Jira go to Settings → Apps → Find new apps and search for License Audit for Jira.
Start the trial
Click Try it free. A 30-day trial starts automatically and rolls into a subscription unless you cancel from Manage apps.
Approve the permissions
Every one is a read permission. The app requests no write access of any kind.
Only Jira site administrators can open the app. Find it under Settings → Apps → License Audit.
Run an audit
Pick a period. Press the button. Come back when it's done.
- Choose a period: No activity in 30, 60, 90, 180 or 365 days.
- Click Run audit.
- The scan runs in the background. You can close the page — it continues, and the result is waiting when you return. On a large site expect a few minutes.
You'll see progress through four stages: reading license groups, listing licensed users, scanning recent activity, and verifying candidates.
Read the report
Two tables, and both of them are about money.
The seat table
For each Jira product on your site — Jira Software, Jira Service Management, Jira Work Management — the seats counted by Atlassian (read directly from your site, the number you're billed for), the seats on your plan, and how many of those seats belong to dormant users.
The dormant list
Each user with the products they hold a seat for — a dormant JSM agent seat and a dormant Jira Software seat cost different amounts — and their last Jira activity: 90–180 days, 90–365 days, or over a year, or never. Sorted longest-dormant first.
Enter your annual cost per seat to see what reclaiming every dormant seat would save per year. Export all as CSV gives you every dormant user in a form you can paste into a spreadsheet or hand to whoever manages licences.
How dormancy is decided
A user is listed only if they did nothing in Jira.
"Something" means any of the four actions below. Two rules follow, and they are the reason the list can be trusted.
Changed a status or any field, or transitioned the issue.
Added or edited a comment on any issue.
Recorded time on any issue.
Created an issue, or is its reporter.
Assignment is something done to a person, not by them. Without this rule, a colleague who left months ago but is still assigned to live tickets would be hidden by other people's edits on those tickets.
The app first scans recent issues to prove most users active quickly, then runs a dedicated check against every issue on your site for anyone it couldn't vouch for. A name reaches the list only after that check finds nothing.
Your data
Nothing leaves Atlassian.
User names, account IDs, product membership, and the author and time of recent issue changes, comments and work logs. It does not read issue text, comment text or attachments.
Only the report and scan progress, in Atlassian's own storage for your site. No issue content, ever.
Nowhere. The app has no servers of its own and makes no requests outside Atlassian.
Everything the app stored is deleted.
Full details in the privacy policy.
Frequently asked
The questions admins ask first.
Someone is listed who I know uses Jira every day.
Check what they do. If they only read issues, or work in boards without changing anything, they leave no trace Jira can report — no app can see logins or page views. If they comment, transition or edit issues they will not appear; if you believe one has, send us their display name and the period and we'll investigate.
Someone is listed who only uses Confluence.
Correct — the app measures Jira activity only. A Confluence-only user holding a Jira seat is exactly a seat worth reviewing.
Why are emails missing for some users?
Their Atlassian profile privacy settings hide the email from apps. Name and account ID are still shown.
The scan says "stuck". Is something wrong?
If a scan makes no progress for 20 minutes the app offers to restart it. Restarting is safe: a scan never changes anything on your site.
Can I cancel a running scan?
Yes, with Cancel. Nothing is changed by starting or cancelling a scan.
The report says the user list came from the site directory.
The app couldn't read your application-role groups, so it listed every active Atlassian account instead — which may include Confluence-only accounts holding no Jira seat. Reinstalling to re-grant permissions usually resolves it.
Does the app deactivate anyone?
No, and it can't — it holds no write permission. Deactivation stays a decision you make in User management, with the list in hand.
How is it priced?
Per user per month, billed by Atlassian on your existing invoice, with a free 30-day trial. The current price is on the Marketplace listing.
Support
Ask the people who built it.
When reporting a problem, include your site URL, the period you ran, and — for a wrongly-listed user — their display name. We never need passwords or tokens.
Get help
One business day, usually much less.
- support@telcomaglobal.com
- Support page
- Known limits, what to include, status
- Response time
- Within one business day