-
Bug
-
Resolution: Fixed
-
High
-
None
-
97
-
Major
-
Issue Summary
When successfully logging in a Cloud site with a Managed Account, the Last Seen information is updated in the Site Administration, while the Last Active in the Organization does not.
Additional comments
- Performed an attempt using Can't Login;
- Performed an attempt authenticating using the credentials.
Environment
- Had SAML SSO set up with Azure and was able to reproduce the behavior;
- Removed the SAML integration and was able to reproduce the behavior.
Steps to Reproduce
- Create an organization and verify your domain;
- Add your site;
- Login using the site URL or http://id.atlassian.com
Expected Results
Both Last Seen and Last Active would be updated.
Actual Results
Only the Last Seen is updated.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
CLOUD-10652 User "Last active" information is not accurate
- Closed
- relates to
-
-
- Closed
-
- is blocked by
-
PC-13655 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[ACCESS-671] Last Active (Organization) and Last Seen (Site Administration) information not syncing
Hi, look at the screenshot
The user logged in today, and yesterday on Jira (and in passed days)
Surely not 6 months ago.
Maybe because is synced with GSuite?
Hi f26569295fe8, last active date should be fixed for all users accessing our products after mid-March - do the affected users in your org fall outside of that?
Hi 4d179111dc69, we are currently testing the code changes and will push to production as soon as we get the all clear.
Hi,
Do you have an estimated date for the resolution of this problem?
Thanks
Last active and last seen timestamps should be consistent for all products (except Jira Service Management and Jira Work Management) since mid June.
Regarding Jira Service Management (JSM) and Jira Work Management (JWM), the fix has already been identified and we are working with Hydra team to get this resolved. Will update the ticket with an ETA for the fix as soon as I have one from the Hydra team.
Hi f26569295fe8, the work to sync the info between Last Active and Last Seen is already scheduled. We'll post an update here when it is completed, which we expect to be soon.
Yiting
Senior Product Manager, Atlassian Cloud
Hi, any news?
Using API, Last Active (Organization) and Last Seen (Site Administration) are still not synced.
Thanks.
Hi a9260f9bf17b, yes as mentioned in bf18feb749e0's comment there are a small number of inconsistencies specifically affecting Jira (which it looks like is the product affected in your screenshots) that we are still fixing up. While we believe we've addressed the main root cause affecting both the number of inconsistencies customers were seeing and the extent (in terms of difference between the dates) there are a few remaining cases we're actively working on addressing.
I've reopened this ticket for clarity and we will close it again once those remaining cases are addressed.
Any ideas?