-
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
-
ACCESS-671 Last Active (Organization) and Last Seen (Site Administration) information not syncing
- Closed
- was cloned as
-
ACCESS-1783 Last Active inform inaccurate time in Users Page
- Long Term Backlog