Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-9979

Last Activity date not updated for users with only site access (JSM customers)

    • 353
    • 145
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Last Activity date not updated for users with only site access

      Steps to Reproduce

      1. Configure JSM
      2. Invite a user from the site administration screen
      3. Don't grant any product access, but grant site access
      4. Log in with that user
      5. Create a JSM issue

      This creates an Atlassian Account user that has access to the portal for JSM only, although they are not portal-only users: Manage Jira Service Management customer accounts

      Expected Results

      Login/activity date should be updated in the Administration > Users screen

      Actual Results

      Last Activity date just shows the date the user was created

      Workaround

      It's possible to find this date based on the date of the most recent comment/issues created by a customer using JQL and sorting by created date. This can also be found through the database.

            [JSDCLOUD-9979] Last Activity date not updated for users with only site access (JSM customers)

            Hi everyone,

            I'm Michelle, the product manager looking into all issues and feature requests related to last active across the Atlassian product suite including JSM.

            Thank you all for sharing your feedback on this ticket, I hear you all and appreciate your patience as I'm currently in the midst of creating a comprehensive overview of the known limitations, gaps and requests concerning last active for JSM.

            While my engineering team and I have been actively working on improving last active over the past few months with improved documentation and addressing other issues, soon I will be able to update you all with more details pertaining to this issue.

            Warm regards,

            Michelle Tan

            Michelle Tan added a comment - Hi everyone, I'm Michelle, the product manager looking into all issues and feature requests related to last active across the Atlassian product suite including JSM. Thank you all for sharing your feedback on this ticket, I hear you all and appreciate your patience as I'm currently in the midst of creating a comprehensive overview of the known limitations, gaps and requests concerning last active for JSM. While my engineering team and I have been actively working on improving last active over the past few months with improved documentation and addressing other issues, soon I will be able to update you all with more details pertaining to this issue. Warm regards, Michelle Tan

            How are admins supposed to audit their JSM customers if we can't see an activity date?  There's literally NO DATA available regarding customer activity in JSM at the organization level.  Do you really expect us to just leave users assigned as customers to a service desk forever?

            Paul Stallworth added a comment - How are admins supposed to audit their JSM customers if we can't see an activity date?  There's literally NO DATA available regarding customer activity in JSM at the organization level.  Do you really expect us to just leave users assigned as customers to a service desk forever?

            I don't understand how this is still not fixed yet, it is a huge issue which creates a lot of mess in larger organisations. Please Atlassian, this really shouldn't be difficult to fix.

            Adam Mäsiar added a comment - I don't understand how this is still not fixed yet, it is a huge issue which creates a lot of mess in larger organisations. Please Atlassian, this really shouldn't be difficult to fix.

            MBradshaw added a comment -

            I don't understand - this used to work until a few weeks ago in my org. Please fix ASAP. I can't roll out JSM to a broader org audience without being able to test what customers are experiencing!

            MBradshaw added a comment - I don't understand - this used to work until a few weeks ago in my org. Please fix ASAP. I can't roll out JSM to a broader org audience without being able to test what customers are experiencing!

            George G added a comment -

            I can't go a day without being redirected to an obvious missing feature and an ignored request. You're making it easier to find alternative products

            George G added a comment - I can't go a day without being redirected to an obvious missing feature and an ignored request. You're making it easier to find alternative products

            Hello together!
            I agree with all the previous speakers. Please implement ASAP!
            This is an important feature and the implementation is not such a big deal!
            Pleeease!!!

            Joachim Rieger (rgjadmin) added a comment - Hello together! I agree with all the previous speakers. Please implement ASAP! This is an important feature and the implementation is not such a big deal! Pleeease!!!

            Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            Tobias Bosshard added a comment - Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            We are not at all satisfied with the response you have provided. For audit purposes, we need to clean up users who have not accessed the portal within a specific timeframe. However, due to the incorrect information, we are deactivating users who actually use the service, leading to numerous complaints every month.

            Working under these circumstances is very challenging, and we see that the ticket has been open for three years without any intention to address it for at least another year. For a company like Atlassian, these are basic standards that should be met. Having to "vote" in the hopes that someone might someday take the ticket into consideration seems pathetic to me.

            I hope someone takes action on this matter.

            Lucila from SEAT

            Lucila Lozano added a comment - We are not at all satisfied with the response you have provided. For audit purposes, we need to clean up users who have not accessed the portal within a specific timeframe. However, due to the incorrect information, we are deactivating users who actually use the service, leading to numerous complaints every month. Working under these circumstances is very challenging, and we see that the ticket has been open for three years without any intention to address it for at least another year. For a company like Atlassian, these are basic standards that should be met. Having to "vote" in the hopes that someone might someday take the ticket into consideration seems pathetic to me. I hope someone takes action on this matter. Lucila from SEAT

            Iliyas Ahemad Siddiqui added a comment - https://getsupport.atlassian.com/browse/PCS-346183

            +1

              Unassigned Unassigned
              dponzio Daniel Ponzio
              Votes:
              108 Vote for this issue
              Watchers:
              113 Start watching this issue

                Created:
                Updated: