-
Bug
-
Resolution: Fixed
-
High
-
None
-
16
-
Severity 3 - Minor
-
Hi Everyone,
The Last Active date went though a rewrite back in 2021, this was done via https://jira.atlassian.com/browse/ID-7598.
I believe most of the issues listed here would have already been fixed from the rewrite.
For others, I think we need to update our documentation to more clearly reflect how the Last Active date works on different pages:
1. On the User list and User details page, the last active date in the top left corner is the last activity we've recorded for that user in any of the products for that site or organization. Usually, it will only include the products listed that the user has access to. But if the user has recently had a product remove from them, it can still reflect their last activity date in the removed product
2. The Last active date in the Managed Account list can be based on a different list of products, some of which may not be in your organization. This date may not match the Last active date in the User List / User details page, since it can be related to different products.
3. The Last login date, which can be seen from the Atlassian Access Audit logs, may not match up to either of the above dates. It is simply the last date the user logged in with their username/password or SSO. It has no relation to activity in a product.
4. The last active date will not refresh if a user is using the JSM Help Centre Portal. This is being addressed in a different ticket.
5. There is a normal delay of 4 to 24 hours for for the Last Active Date to be updated across all products.
6. It can be quite normal to have no correlation between the Last Active Date on a user profile in User Management vs the Last Active time on a Managed Account that is inactive for a long time
I hope that information is useful. Please do make a comment on this ticket if you think you're still experiencing incorrect Last Activity dates, but consider the above first.
We will be making changes to our UI and documentation to make this clearer, and help customers better understand date differences.
Summary
When we take a look at the User Management, the Last Active field displays a date and time, for customers which are inactive for a long time, it displays that they logged on worked on inaccurate dates. This can be confirmed by looking at the Atlassian Account logs since it has a Last Active field. On Atlassian Account, we can see that the user is inactive for more time than displayed in the Cloud Instance User Management.
Environment
Cloud, User Management
Steps to Reproduce
- Open a user profile on User Management that is inactive for a long time
- Compare with Atlassian Account Last Active time
- Times will be different
Expected Results
The Last Active is inaccurate.
Actual Results
Last Active field should display the right date and time.
Workaround
No Workaround for customers.
- is related to
-
-
- Closed
-
- was cloned as
-
-
- Long Term Backlog
-
[ID-8046] Last Active inform inaccurate time
Hi, Im unsure of what you are saying considering that one of my users was provably active today and shows as inactive since February Feb 21, 2023 what is the appropriate venue to reopen a ticket
Our analysis shows that the Last Active date has not be incorrect for any of the related support tickets for a number of months.
We consider this bug to be closed now.
Hi Kieren,
After replying to your mail on October 11, I have not received any answer.
Should I follow up on this issue or will I receive your news by mail?
This issue is critical in order to deactivate users who are not logging in to Jira.
Thanks
Kind regards
Hello Kieren,
that was great news you indicated because this issue has been reported for years now and it is really critical for the identification of inactive users.
However, I have done a test and found a bad new one.
I tested with a user and in his detail appears the date of last activity for 2019, however this user created an issue in 2022 
Are you sure that the issue is considered solved by Atlassisan?
Thanks
Hi Everyone,
I've just been informed of this ticket.
The Last Active date went though a rewrite back in 2021, this was done via https://jira.atlassian.com/browse/ID-7598.
I believe most of the issues listed here would have already been fixed from the rewrite.
For others, I think we need to update our documentation to more clearly reflect how the Last Active date works on different pages:
- On the User list and User details page, the last active date in the top left corner is the last activity we've recorded for that user in any of the products for that site or organization. Usually, it will only include the products listed that the user has access to. But if the user has recently had a product remove from them, it can still reflect their last activity date in the removed product
- The Last active date in the Managed Account list can be based on a different list of products, some of which may not be in your organization. This date may not match the Last active date in the User List / User details page, since it can be related to different products.
- The Last login date, which can be seen from the Atlassian Access Audit logs, may not match up to either of the above dates. It is simply the last date the user logged in with their username/password or SSO. It has no relation to activity in a product.
- The last active date will not refresh if a user is using the JSM Help Centre Portal. This is being addressed in a different ticket.
- There is a normal delay of 4 to 24 hours for for the Last Active date to be updated across all products.
I hope that information is useful? Please let me know if you're still experiencing unexpected Last Activity dates.
Hi,
how are you?
I have had no response to my last queries in previous notes (march, april, may, jul).
What can we do to get this issue selected for resolution or get an alternative?
Thank you very much for your consideration.
Since this was logged in 2017 and has actively been ignored by Atlassian, we have had to explore alternative applications instead.
Hi,
how are you?
I have had no response to my last queries in previous notes (march, april, may).
What can we do to get this issue selected for resolution or get an alternative?
Thank you very much for your consideration.
Hello Kieren,
I have been seeing the data correctly for a few weeks now.
However the bug existed and at the time I presented the evidence.
As of today I understand that it is corrected, at least I have not found inconsistencies.
Thank you.