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

Last active column in managed accounts export file does not consider portal access

XMLWordPrintable

    • 8
    • 2

    • 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

      When exporing the CSV list of managed accounts, the column E of the CSV file shows the "Last active" date for that account. This column does not reflect the login in JSM portal, even though the authentication happens on the id platform (with SAML, if enforced)

      Steps to Reproduce

      1. Have an organization with some managed accounts
      2. One of the accounts has access to a JSM portal
      3. The user logs in to the portal and raises a ticket

      Expected Results

      The CSV file should show the "Last active" date the date when the user logged-in to the portal

      Actual Results

      The CSV file shows the last active date the date when the user logged-in to a product with full user access (licensed account)

      Workaround

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

          Form Name

            [JSDCLOUD-10609] Last active column in managed accounts export file does not consider portal access

            Michael Ziegler added a comment -

            not only from GDPR point of view: we need this feature as well like b1c6c1f583af mentioned above

            Michael Ziegler added a comment - not only from GDPR point of view: we need this feature as well like b1c6c1f583af mentioned above

            Thomas Fuerer added a comment - - edited

            This is a serious blocker to us. We executed a bulk deletion 3 times now and need to rollback because the data cannot be trusted.

            Problem in detail:
            We want to delete/deactivate every user which do not have any product access or never used his/her account.
            For the future we need to keep our organization cleaned by executing a regular job which deactivates all users in the organization which are retired.

            Thomas Fuerer added a comment - - edited This is a serious blocker to us. We executed a bulk deletion 3 times now and need to rollback because the data cannot be trusted. Problem in detail: We want to delete/deactivate every user which do not have any product access or never used his/her account. For the future we need to keep our organization cleaned by executing a regular job which deactivates all users in the organization which are retired.

              Unassigned Unassigned
              clionte Claudiu Lionte (Inactive)
              Votes:
              30 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: