Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-671

Last Active (Organization) and Last Seen (Site Administration) information not syncing

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • PLAT - Hydra
    • None

      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

      1. Create an organization and verify your domain;
      2. Add your site;
      3. 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

            [ACCESS-671] Last Active (Organization) and Last Seen (Site Administration) information not syncing

            Any ideas?

            Maurizio Masala added a comment - Any ideas?

            Maurizio Masala added a comment - - edited

            Hi, look at the screenshot

            https://imgur.com/RJ8U86r

            The user logged in today, and yesterday on Jira (and in passed days)

            Surely not 6 months ago.
            Maybe because is synced with GSuite?

            Maurizio Masala added a comment - - edited Hi, look at the screenshot https://imgur.com/RJ8U86r The user logged in today, and yesterday on Jira (and in passed days) Surely not 6 months ago. Maybe because is synced with GSuite?

            Kat N added a comment -

            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? 

            Kat N added a comment - 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 @Kat N

            When do you expect to release the fix?

            Thanks.

             

            Bye.

            Maurizio Masala added a comment - Hi @Kat N When do you expect to release the fix? Thanks.   Bye.

            Kat N added a comment -

            Hi 4d179111dc69, we are currently testing the code changes and will push to production as soon as we get the all clear. 

            Kat N added a comment - 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

            Ramiro Justet added a comment - Hi, Do you have an estimated date for the resolution of this problem? Thanks

            Ameya Lad added a comment -

            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.

            Ameya Lad added a comment - 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.

            Yiting Jin (Inactive) added a comment - - edited

            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

            Yiting Jin (Inactive) added a comment - - edited 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.

            Maurizio Masala added a comment - Hi, any news? Using API, Last Active (Organization) and Last Seen (Site Administration) are still not synced.   Thanks.

            Dave Meyer added a comment -

            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.

            Dave Meyer added a comment - 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.

            Rishi Dhar added a comment - - edited

            Thanks for the detailed explanation Dave!

            We have several users that have a newer "Last Seen" date on site level and an older "Last Active" date on org level. I guess that's where the confusion arises from. In your screenshots that user's "Last Seen" and "Last Active" are the same date but for a lot of our users the "Last Seen" on org level is a newer date than "Last Active". We aren't sure why this is

            Example:

            Org Level "Last Active": March 7th 2021

            Site Level "Last Seen": March 9th 2021

             
            https://imgur.com/m3BFnDx

            https://imgur.com/sOtQ5eu

             

             

             

            Rishi Dhar added a comment - - edited Thanks for the detailed explanation Dave! We have several users that have a newer "Last Seen" date on site level and an older "Last Active" date on org level. I guess that's where the confusion arises from. In your screenshots that user's "Last Seen" and "Last Active" are the same date but for a lot of our users the "Last Seen" on org level is a newer date than "Last Active". We aren't sure why this is Example: Org Level "Last Active": March 7th 2021 Site Level "Last Seen": March 9th 2021   https://imgur.com/m3BFnDx https://imgur.com/sOtQ5eu      

            Hi a9260f9bf17b,

            Since each user's Atlassian account can have access to multiple products, "activity" is not correlated with "logins" (I can log in to to my account and then navigate seamlessly between multiple Jira and Confluence instances).

            At the org administration level, for an organization's managed accounts, we report the "last active" date for each product (and instance, in the case of Jira and Confluence) a user has access to. This date is based on any type of user activity on the product. We then provide an aggregated "last active" date for the account that's based on the last time the user was active in any product.

            At the site administration level, we report the date the user was last seen in each product on that site. I've attached some example screenshots that show this.

            Dave Meyer added a comment - Hi a9260f9bf17b , Since each user's Atlassian account can have access to multiple products, "activity" is not correlated with "logins" (I can log in to to my account and then navigate seamlessly between multiple Jira and Confluence instances). At the org administration level, for an organization's managed accounts, we report the "last active" date for each product (and instance, in the case of Jira and Confluence) a user has access to. This date is based on any type of user activity on the product. We then provide an aggregated "last active" date for the account that's based on the last time the user was active in any product. At the site administration level, we report the date the user was last seen in each product on that site. I've attached some example screenshots that show this.

            Rishi Dhar added a comment -

            So does the org level `Last Active` represent a login into any Atlassian service (Jira, Confluence, Trello, etc)? Or does it relate to an activity or action taken in a particular product

            Rishi Dhar added a comment - So does the org level `Last Active` represent a login into any Atlassian service (Jira, Confluence, Trello, etc)? Or does it relate to an activity or action taken in a particular product

            Rishi Dhar added a comment -

            Is this being worked on? The last_active date needs to be accurate in order to be used.

            Rishi Dhar added a comment - Is this being worked on? The last_active date needs to be accurate in order to be used.

            John Price added a comment -

            Side note:  When doing inactive user cleanup last week, I found that the Last Seen In values for Jira users had changed dramatically (now more accurate).  I have not checked the Managed Users Directory, but I can confirm that Last Seen dates for Jira are better.  I happened to have CSV exports of the same users from 1/2/3 months ago and when comparing the dates it's clear that a lot suddenly shifted last week.  Support confirmed that changes were made to the code.  It's good, because I can clean up more users.

            Still not sure if we can rely on dates in Managed Users Directory yet.

            John Price added a comment - Side note:  When doing inactive user cleanup last week, I found that the Last Seen In values for Jira users had changed dramatically (now more accurate).  I have not checked the Managed Users Directory, but I can confirm that Last Seen dates for Jira are better.  I happened to have CSV exports of the same users from 1/2/3 months ago and when comparing the dates it's clear that a lot suddenly shifted last week.  Support confirmed that changes were made to the code.  It's good, because I can clean up more users. Still not sure if we can rely on dates in Managed Users Directory yet.

            bf18feb749e0 - this will be difficult for me to debug on my own because I don't seem to have access/knowledge to how the data is assembled within the web front end you're viewing. It is not necessarily guaranteed that the data your are viewing is a) untransformed, and b) solely from the Hydra API.

            I can say that I do have access and knowledge of the bdm-user entity (via Hydra API), which is where I believe this information you're seeing is pulling from:

            Things I will need:

            Additionally, I searched the following ticket to attempt to reproduce the issue: https://getsupport.atlassian.com/browse/PSCLOUD-49316

            It appears the user described in this issue, at the time of writing, has consistent (day granularity) profile_last_modified and product_access.last_active_timestamp dates of 1.5931108478E12 and 2020-06-25T00:00:00.000Z, respectively. Note that the former timestamp is unix epoch and translates into Thursday, June 25, 2020 6:47:27.800 PM.

            My recommendation for debugging this issue is to:

            • Verify the above assumptions are correct (front end / back end translations)
            • Create a new user / site / etc that reproduces the issue you are describing
            • Please let me know when the condition has been recreated and I can check the back end transformations and data to ensure they are in agreement with your expectations
            • Bugfix if needed

            It is possible, but difficult/time consuming to recreate a former state within Hydra since the API uses a 'most recent' version of the bdm. As such, recreating the condition with a new user will be our fastest path to resolution. Appreciate your support  

            Gregory Godreau added a comment - bf18feb749e0 - this will be difficult for me to debug on my own because I don't seem to have access/knowledge to how the data is assembled within the web front end you're viewing. It is not necessarily guaranteed that the data your are viewing is a) untransformed, and b) solely from the Hydra API. I can say that I do have access and knowledge of the bdm-user entity (via Hydra API), which is where I believe this information you're seeing is pulling from: Things I will need: Knowledge of how the last seen field is presented in your web front end. I believe the metric that is being presented is the product_access.last_active_timestamp field: https://bitbucket.org/atlassian/streamhub-schema-service/src/74386e90ff491a4b7b6d2769810d7fd968b5b175/schemas/it-bdm/user-schema-v2.5.json#lines-206 Knowledge of how the Last active metric is presented in your web front end. I believe this is the profile_last_modified field from the user entity within the Hydra API: https://bitbucket.org/atlassian/streamhub-schema-service/src/74386e90ff491a4b7b6d2769810d7fd968b5b175/schemas/it-bdm/user-schema-v2.5.json#lines-155 Additionally, I searched the following ticket to attempt to reproduce the issue: https://getsupport.atlassian.com/browse/PSCLOUD-49316 It appears the user described in this issue, at the time of writing, has consistent (day granularity) profile_last_modified and product_access.last_active_timestamp dates of 1.5931108478E12 and 2020-06-25T00:00:00.000Z , respectively. Note that the former timestamp is unix epoch and translates into Thursday, June 25, 2020 6:47:27.800 PM . My recommendation for debugging this issue is to: Verify the above assumptions are correct (front end / back end translations) Create a new user / site / etc that reproduces the issue you are describing Please let me know when the condition has been recreated and I can check the back end transformations and data to ensure they are in agreement with your expectations Bugfix if needed It is possible, but difficult/time consuming to recreate a former state within Hydra since the API uses a 'most recent' version of the bdm. As such, recreating the condition with a new user will be our fastest path to resolution. Appreciate your support  

            John Price added a comment -

            I found this today when trying to script user cleanup via API.  Let's say I want to revoke Jira access for users who have not been active in 1 year:

            1) I query the Users API for the org and find people with a very old last_active date.

            2) I go look in the app user admin for Jira (not the Managed Users page) and look at the "Last Seen on Site" value for Jira.

            Expected: They are the same.

            Actual: Last Seen on Site is much newer in some cases.

            This is bad because if I script this, I'll end up disabling users who are still using the app.

            John Price added a comment - I found this today when trying to script user cleanup via API.  Let's say I want to revoke Jira access for users who have not been active in 1 year: 1) I query the Users API for the org and find people with a very old last_active date. 2) I go look in the app user admin for Jira (not the Managed Users page) and look at the "Last Seen on Site" value for Jira. Expected: They are the same. Actual: Last Seen on Site is much newer in some cases. This is bad because if I script this, I'll end up disabling users who are still using the app.

              fe351cdb72b6 Gaurang Kher
              cfraga Caio
              Affected customers:
              66 This affects my team
              Watchers:
              92 Start watching this issue

                Created:
                Updated:
                Resolved: