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; } } }

How can we report true last login dates in Jira when "Last Seen" only tracks edits, not views?

Radia Dev

Hi Community folks,

Hope everyone is doing well!

I have a quick question regarding the "Last Seen" date in Atlassian Administration (User Management).

When checking a user's profile, there is a "Last Seen" date shown for each product. However, while doing a license cleanup, I noticed that this date only seems to update when a user performs an active modification (like editing a ticket). If a user merely logs in and views/reads tickets on a day-to-day basis, the "Last Seen" timestamp does not update at all.

Because read-only viewing still consumes a Jira license, the current timestamp doesn't accurately reflect whether a user is truly active or dormant.

Does anyone know how to extract an accurate list or report of users based on their actual last login/visit date (including read access)?

Thanks in advance for your insights!

Accepted answers

All comments

Fazila Ashraf

Hi @Radia Dev

With no real work arounds, we still use the last seen with lots of buffer to skip such users entries. Unfortunately this also do not capture API token based actions as well.

There is an open suggestion https://jira.atlassian.com/browse/AX-2044 which i recommend to upvote and watch.

Tomislav Tobijas

Hi @Radia Dev ,

Yeah... 🫤 This is a known limitation and it's tracked here:

As a workaround, you could try one of these:

Organization Audit Log: If you have an Atlassian Guard Standard or Premium subscription, you can track actual login frequencies. Navigate to admin.atlassian.com > Insights > Audit Log, filter the Activity by Logged in to account, and export the results to a CSV to analyze login dates

REST API: You can programmatically extract login events using the endpoint GET /admin/v1/orgs/{orgId}/events?action=login (this also requires Atlassian Guard)

I know the audit log supports/contains this info, but I've never pulled it via the REST API (although it makes sense it will actually work).

Hope this helps.

Cheers,
Tobi

Radia Dev

Hi @Tomislav Tobijas ,

I appreciate your thoughts on this matter!

The ticket has been upvoted by me. The workaround makes perfect sense, and I'll investigate!

Thanks,

Dev.

Trudy P Claspill

I wonder if this affects the "last activity" evaluation used to determine if a Free subscription has been inactive for an extended period of time...

Tomislav Tobijas

@Trudy P Claspill it's not (or at least shouldn't be) related. Although for my free sites, whenever I get a deactivation notice email, I like to be sure and then simply perform an action (e.g., create a new work item, delete the existing/dummy one, and such).

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jsm