nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Identification of Inactive Jira Users in Bulk

Kumari Dvipa_8fw18g

Hi There,

Hope you are doing well.

I am looking for a way to identify users who have not logged in to Jira for a long period (for example, the last 90 days) so their accounts can be deactivated. In this context, inactive users are those who have not logged in to Jira for an extended period of time.

Could you please advise on how we can identify inactive users?

Thank you for your time.

Regards,
Dvipa

Accepted answers

All comments

Arkadiusz Wroblewski

Hello @Kumari Dvipa

In Jira Cloud, inactivity is checked in Atlassian Administration using the Last active data. As a Product Admin you typically won’t have access to export it.

Ask an Org Admin / Site Admin / User access admin to export users and filter >90 days, then remove product access / suspend.

https://developer.atlassian.com/cloud/admin/organization/user-last-active-dates/

Marc -Devoteam-

Hi @Kumari Dvipa

@Arkadiusz Wroblewski is right but sometimes the information is not correct, based on that a user could also use Trello, or is able to access other Jira cloud instances, based on using the same email address, especially if its a managed account

There are some good option on the marketplace to manage this.

I like, see; Flexible User License - Auto User Management for Jira

Kumari Dvipa_8fw18g

Hello @Marc -Devoteam- @Arkadiusz Wroblewski

Thank you for your message I will check both option.

Also, Can we use JQL or Automation for this?

Thank you,

Dvipa

Marc -Devoteam-

HI @Kumari Dvipa

No this can't be done by JQL.

Via API you can disable or suspend users, but you can't get last login information.

Arkadiusz Wroblewski

@Marc -Devoteam-

Good point, buddy!

I mostly do it via export. And btw, depending on how big the instance is: it used to be easier under the old Atlassian user billing policy. After the policy changes, you still pay the difference because they moved to “slot-based” billing. So regular reviews make a lot of sense in big instances. In smaller ones, I’d say it depends on the need and cost optimization.

Yup, Marketplace have couple usefull Apps.

Mahima_miniOrange

Hi @Kumari Dvipa

Yes, identifying inactive users is a common requirement, especially when you want to optimize licenses and deactivate accounts that have not been used for a long time.

To address this, you can use Automated User Management for Jira app, which allows admins to easily identify users who have not logged in for a specific period (for example, 30, 60, or 90 days). With the app, you can:

Identify inactive users based on their last login activity
Automatically deactivate users who have not logged in for long period
Bulk deactivate users directly if required

This makes it much easier to manage inactive accounts without manually reviewing user activity.

If you are open to exploring the app-based approach, I would be happy to share more details or help you set up a demo call or trial so you can evaluate it in your environment.

Looking forward to your thoughts.

Best regards,
Mahima
miniOrange

Arkadiusz Wroblewski

@Kumari Dvipa

As @Marc -Devoteam- already mentioned before, unfortunately, you can’t do that.

He also mentioned too, take a look on Marketplace, there´s couple good Apps for that.

James - Seats Management

Great question — this is something almost every Jira admin deals with eventually.

Here's a practical approach:

1. Export your user list from Atlassian Admin (admin.atlassian.com > Users). You can see last active dates there.

2. Filter for users inactive beyond your threshold (60-90 days is common). Sort by last active date to identify the biggest offenders.

3. Before deactivating, segment by product — a user might be inactive in Jira but active in Confluence. Deactivating them from the org would remove all product access.

4. For ongoing cleanup, the manual export approach works but needs to be repeated regularly. There are Marketplace apps that automate this on a daily basis.

One option is User Management Automation (https://marketplace.atlassian.com/apps/1230326/user-management-automation-for-jira-confluence) — it runs daily across all Atlassian products, handles both managed and unmanaged accounts, and is Forge-native so data stays within Atlassian. Full disclosure: I built this.

But regardless of the tool, the key insight is: don't do this as a quarterly audit. With Atlassian's MQB billing, every inactive seat that stays active for even one day in a billing cycle costs you for the full month. Daily automation pays for itself quickly.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

cloud

jira-cloud

confluence-cloud