Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-93

User status at User Management still showing "No activity" even though the user has logged in to the instance

    • 33
    • Severity 3 - Minor

      Issue Summary

      User status still displays No Activity even after the user already logged in to the instance. When open their profile , it show Never seen on this site

      Environment

      Cloud

      Steps to Reproduce

      1. As site-admin , invite a user
      2. Go to the user email inbox, he should receive invitation email from JIRA
      3. Complete the registration and login to the instance.
      4. Create an issue or view any issue

      Expected Results

      User status from User Management page doesn't show "No Activity" and in the profile updated with Last Seen information

      Actual Results

      User status from User Management page show "No Activity" and in the profile show "Never seen on this site"

      Notes

      It will not affect the user login. Note that the last activity data can be delayed up to 4 hours.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JWMCLOUD-93] User status at User Management still showing "No activity" even though the user has logged in to the instance

            This is still happening in September 2023 and needs to be reopened and corrected. We migrated from on-prem to Cloud JSM a month ago and it worked for the first few days and then stopped. Any new users that activate their account are still showing as "Never logged into site." I have had a support ticket open with Praecipio on this issue for 4 weeks with no movement. I was just directed to this closed ticket and I am shocked that this was marked as resolved and closed. My users are senior VP's and Directors and I cannot email them numerous times asking them to "validate their account" again. I cannot troubleshoot by impersonating or reset the users password. As an Org Admin I cannot do my job for my customers at our company.

            Please reopen this ticket to actually resolve this issue for all Jira products.

            Como, Jacqueline:(BSC - TSA) added a comment - This is still happening in September 2023 and needs to be reopened and corrected. We migrated from on-prem to Cloud JSM a month ago and it worked for the first few days and then stopped. Any new users that activate their account are still showing as "Never logged into site." I have had a support ticket open with Praecipio on this issue for 4 weeks with no movement. I was just directed to this closed ticket and I am shocked that this was marked as resolved and closed. My users are senior VP's and Directors and I cannot email them numerous times asking them to "validate their account" again. I cannot troubleshoot by impersonating or reset the users password. As an Org Admin I cannot do my job for my customers at our company. Please reopen this ticket to actually resolve this issue for all Jira products.

            Michael Merrifield added a comment - - edited

            I'm not as concerned about activity timestamps.

            I am frustrated that I could previously look up a user and see that they have at least activated their account in our instance.

            The current behavior gives me absolutely zero feedback that a user has activated their account. That seems like a regression from my perspective. If the user has trouble logging in, I have not feedback from the admin user management site about their status. I can't attempt to log in as them or send a password reset. Both of these tools were previously available to me as well as the information that they activated their account (i.e. it does NOT say "No activity" or "Never seen on this site"). Now ALL users report this way...

            My only tool available for troubleshooting is to resent an invitation... which would be really annoying to receive if you already acted on it but now can't log in...

            For users with site access but no product access, the following is misleading and in fact wrong when this user has in fact activated their account, logged into the portal, created issues, etc.

            [x] Has access on site

                 Never seen on this site

            If a subtle distinction somehow makes this correct for this type of user, it's useless to me.

            Michael Merrifield added a comment - - edited I'm not as concerned about activity timestamps. I am frustrated that I could previously look up a user and see that they have at least activated their account in our instance. The current behavior gives me absolutely zero feedback that a user has activated their account. That seems like a regression from my perspective. If the user has trouble logging in, I have not feedback from the admin user management site about their status. I can't attempt to log in as them or send a password reset. Both of these tools were previously available to me as well as the information that they activated their account (i.e. it does NOT say "No activity" or "Never seen on this site"). Now ALL users report this way... My only tool available for troubleshooting is to resent an invitation... which would be really annoying to receive if you already acted on it but now can't log in... For users with site access but no product access, the following is misleading and in fact wrong when this user has in fact activated their account, logged into the portal, created issues, etc. [x] Has access on site      Never seen on this site If a subtle distinction somehow makes this correct for this type of user, it's useless to me.

            Hi Keri,

            Were tests only conducted on Work Management though? What about Jira and Jira SM?

            This issue has been happening when we use the Admin UI forever now. It happens everyday with all new users that are added to Atlassian - at least on my instance. And I've seen people complain about this issue for a long time so I don't understand how this ticket can be closed, honestly. Not sure why this ticket was opened with Work Management when it happens for all other products as well.

            Is there a chance you can clone and move this ticket to a more generic Cloud project since it already has all the details, voters, people watching, etc.?

            Asking users to create another bug is a bit of a stretch here imo...

            Than you.

            Ricardo.Gomes added a comment - Hi Keri, Were tests only conducted on Work Management though? What about Jira and Jira SM? This issue has been happening when we use the Admin UI forever now. It happens everyday with all new users that are added to Atlassian - at least on my instance. And I've seen people complain about this issue for a long time so I don't understand how this ticket can be closed, honestly. Not sure why this ticket was opened with Work Management when it happens for all other products as well. Is there a chance you can clone and move this ticket to a more generic Cloud project since it already has all the details, voters, people watching, etc.? Asking users to create another bug is a bit of a stretch here imo... Than you.

            Matt Di Berardino added a comment - - edited

            Hi b032fe1ac0d1,

            We have investigated the problem on our end and have not found any issue with the last access field in the Jira admin UI for Jira Work Management projects after the data pipeline incident has been resolved on 29th of July, 2022.

            However, if you still experience an issue with this, please raise a support ticket at https://support.atlassian.com to allow our support teams to investigate the issue with your specific tenant context. We are not able to access your data without your explicit consent, which is why we can only perform this investigation through a support case. I hope you understand.

            I apologise for the inconvenience that this issue is causing and I hope we can resolve your problem soon.

            Kind regards,
            Matt Di Berardino
            Jira Work Management Developer

            Matt Di Berardino added a comment - - edited Hi b032fe1ac0d1 , We have investigated the problem on our end and have not found any issue with the last access field in the Jira admin UI for Jira Work Management projects after the data pipeline incident has been resolved on 29th of July, 2022. However, if you still experience an issue with this, please raise a support ticket at https://support.atlassian.com  to allow our support teams to investigate the issue with your specific tenant context. We are not able to access your data without your explicit consent, which is why we can only perform this investigation through a support case. I hope you understand. I apologise for the inconvenience that this issue is causing and I hope we can resolve your problem soon. Kind regards, Matt Di Berardino Jira Work Management Developer

            Mine is working now also.

            Lucia Cumpson added a comment - Mine is working now also.

            Mine started July 19th and the last activity is giving correct details now..I think they only fixed it for those that had the issue on July 19th.

            Ismail Sanni added a comment - Mine started July 19th and the last activity is giving correct details now..I think they only fixed it for those that had the issue on July 19th.

            Keri Mason added a comment -

            We are talking about two different things if this started on " 19th July, 2022"  if you notice all of our comments on this BUG is from before July 19. Still broken and still an issue. Why won't they fix this bug?

            Keri Mason added a comment - We are talking about two different things if this started on " 19th July, 2022"  if you notice all of our comments on this BUG is from before July 19. Still broken and still an issue. Why won't they fix this bug?

            Hi everyone,

            A recent incident that impacted our data pipeline caused all timestamps for product access to stop updating since 19th July, 2022. The incident was resolved on 29th July, 2022. During that timeframe, the last activity date in the Jira Admin UI has been wrongly showing an older timestamp or no activity at all for product access.

            The incident has now been resolved and last access details are correctly gathered and populated in the Jira Admin UI.

            Please note that the access events data aggregation is not instant and the last activity details can appear in the admin UI with a delay of up to 5 hours.

            Thank you for your patience and we apologise for the impact this issue may have caused.

            Kind regards,
            Matt Di Berardino
            Jira Work Management Developer

            Matt Di Berardino added a comment - Hi everyone, A recent incident that impacted our data pipeline caused all timestamps for product access to stop updating since 19th July, 2022. The incident was resolved on 29th July, 2022. During that timeframe, the last activity date in the Jira Admin UI has been wrongly showing an older timestamp or no activity at all for product access. The incident has now been resolved and last access details are correctly gathered and populated in the Jira Admin UI. Please note that the access events data aggregation is not instant and the last activity details can appear in the admin UI with a delay of up to 5 hours. Thank you for your patience and we apologise for the impact this issue may have caused. Kind regards, Matt Di Berardino Jira Work Management Developer

            Keri Mason added a comment -

            Why was this ticket closed when this is still broken and still an issue?

            Keri Mason added a comment - Why was this ticket closed when this is still broken and still an issue?

            This needs to be fixed. I have several users who are active and showing as "Invited". I absolutely need to know which are really active and which aren't.

            Lucia Cumpson added a comment - This needs to be fixed. I have several users who are active and showing as "Invited". I absolutely need to know which are really active and which aren't.

              yjutard yjutard (Inactive)
              nroslan Atiqah Roslan
              Affected customers:
              18 This affects my team
              Watchers:
              65 Start watching this issue

                Created:
                Updated:
                Resolved: