How to track inactive users from jira?

[Md_ Abrarul Huda]

Is there a way to track users who have not used Jira for a certain amount of time?

I want to generate an alert or automatically deactivate the users that have not been regularly using Jira.

[Ed Letifov _TechTime - New Zealand_]

Hello, @Md_ Abrarul Huda 

I predict that eventually every single vendor from Atlassian Marketplace who is tracking "inactive users" term will show up here :)

There is no native solutions. There are now plenty (way too many) apps — just search for "user management" on Atlassian Marketplace. Ours is one of them.

As I put it in my reply to some comments there is a reason why these apps exist as apps, and why multiple customers trust vendors to do this job instead of doing it themselves, writing scripts, or waiting for Atlassian: predictability of automation, audit logs, flexibility of configuration, no-code-couple-of-clicks approach, security and forward compatibility with Atlassian changes, and more...

[Nayan_miniOrange]

Hi @Md_ Abrarul Huda,

If you're looking for an automated solution, you may want to consider Automated User Management & Auto-deactivation for Jira by miniOrange.

The app is designed specifically for inactive-user management and license optimization across Jira, Confluence, JSM, and Bitbucket. It allows you to:

• Track user inactivity using global or product-specific last login/activity data
• Create scheduled rules to automatically deactivate, suspend, or remove product access for users who have been inactive for a configurable number of days
• Include or exclude users who have never logged in
• Protect admins and service accounts by excluding specific groups from automation
• Run rules in Audit Mode first to see which users would be affected before making any changes
• Send email notifications to users before access is removed
• Review all actions through detailed audit logs, with rollback support for scheduler runs

For organizations looking to reduce license costs while maintaining governance and compliance, it provides a no-code alternative to building custom scripts with Atlassian APIs.

Happy to answer any questions about the use case or configuration.

Thanks,
Nayan Kakuste

[Tomislav Tobijas]

Hey @Md_ Abrarul Huda ,

On top of what Trudy and Arkadiusz said, I know our team test and even implemented a couple of projects with these two:

• User Management and License Optimizer for Jira & Confluence 
• Flexible User License - Auto User Management for Jira 

Now, I'm also trying to find a decent native solution for this. I was thinking of building an API script, but never got around to it.

Anyway, the newest idea is - when they deploy that Rovo will be able to crawl through Atlassian Administration (see ROVO-283), then I'll try to build an agent that checks last activity dates for site users and potentially perform some actions for those who have been inactive for more than 30/60 days. 🤔
It's still purely conceptual, but I believe it could/should work.

Cheers,
Tobi

[Arkadiusz Wroblewski]

@Tomislav Tobijas 

I saw an Atlassian Champion playing around with something similar in Rovo, although I do not remember exactly where.

So yes, Rovo could definitely be capable of doing something like that. In the end, it is doing something similar to what a human would do, touching Endpoints but with algorithmic analysis of the data it receives.

[Md_ Abrarul Huda]

Hey  @Tomislav Tobijas 

Thanks for your input. Going to explore these. But I was looking for a built in option. Not a separate paid option. If possible.

[Ed Letifov _TechTime - New Zealand_]

@Tomislav Tobijas @Arkadiusz Wroblewski 

Can Rovo call Atlassian Org APIs – sure. Just make sure you know EXACTLY who to blame when it does a mistake and deactivates your CEO or some account that you rely on for integration. 

I am saying this from the point of view of a user management app vendor — there is a reason why these apps exist and allow you to configure a STABLE policy that is executed automatically in a PREDICTABLE way i.e. "automation" not "AI confabulation" — because humans too make these mistakes all the time.

Writing a script is a solution, yes — when we sponsor conferences we talk to many customers who have do so. Not a single one wants to maintain the result and worry about breaking changes by Atlassian. It just makes no economic sense. 

[Trudy P Claspill]

Hello @Md_ Abrarul Huda 

There is not a native method to do this through the UI. It requires use of the APIs or third party apps.

There is a suggestion to add this functionality.

https://jira.atlassian.com/browse/JRACLOUD-2841

Two apps suggested by Google are

https://marketplace.atlassian.com/apps/1231176/user-management-extension-manage-inactive-users

https://marketplace.atlassian.com/apps/1230326/user-management-automation-for-jira-confluence

The following came from Google as a method to solve this using the API. I have not tested it out myself:

1. Retrieve Last Active Dates: Use this endpoint to view the last active timestamp for each user across your product instances. 

admin/v1/orgs/{orgId}/directory/users/{accountId}/last-active-dates

2. Deactivate Users: If a user's last_active date exceeds your organization's specified timeframe, you can script a deactivation call using the Jira Cloud user management API. [4]  

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

[Arkadiusz Wroblewski]

Hello @Md_ Abrarul Huda 

Track this by separating reporting from deactivation. For reporting, go to admin.atlassian.com> Directory> Users > Export users to pull a CSV containing "Last seen in Jira" data.

For deactivation, avoid native Jira Automation, which is built for issues, not account management. Instead, use external scripts via Atlassian Admin APIs, identity provider (SCIM) lifecycle rules, or Marketplace apps. Always include a manual review or notification step first so you don't accidentally cut off critical service accounts or occasional stakeholders.

Best,

Arkadiusz 🤠☀️😎

[Md_ Abrarul Huda]

Thanks @Arkadiusz Wroblewski

Seems like I have to try to go the API route. Does not seem to have a built-in way.