Uploaded image for project: 'Identity'
  1. Identity
  2. ID-7043

Deleted users keep showing on People Directory and it's not possible to see its profile

      Summary

      • After deleting a user from a Jira/Confluence instance, this user is still showing on the People Directory. Additionally, if we try to click on the user to see its profile we get an error message saying: "Something went wrong. We keep track of these errors, but feel free to contact us if refreshing doesn’t fix things."

      Environment

      • Cloud

      Steps to Reproduce

      1. Interact with a user to make it appear in the People Directory page
      2. Remove the user from the instance
      3. Go to the People Direct page again

      Expected Results

      • The user won't show in the People Directory page after being removed from the instance

      Actual Results

      • The user is still appearing in the People Directory page and if you click on it you will be redirected to a page showing the message: "Something went wrong. We keep track of these errors, but feel free to contact us if refreshing doesn’t fix things."

      Workaround

      • Interact with other users to change the ones that appear in the People Directory page.

            [ID-7043] Deleted users keep showing on People Directory and it's not possible to see its profile

            Eduarda Franck made changes -
            Link New: This issue was cloned as ID-7850 [ ID-7850 ]
            Blake Riosa (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Blake Riosa (Inactive) made changes -
            Assignee New: Blake Riosa [ briosa ]

            We have removed deleted and deactivated users appearing in the People directory as of 2nd August 2019.

            Blake Riosa (Inactive) added a comment - We have removed deleted and deactivated users appearing in the People directory as of 2nd August 2019.
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            André K. (Inactive) made changes -
            Component/s New: Atlassian account profile details [ 56705 ]
            Component/s New: Manage Profile [ 56290 ]
            André K. (Inactive) made changes -
            Key Original: CLOUD-10864 New: ID-7043
            Workflow Original: OnDemand v1 - Restricted [ 3310594 ] New: JAC Bug Workflow v3 [ 3318496 ]
            Project Original: Atlassian Cloud [ 14613 ] New: Identity [ 16810 ]
            Status Original: Open - untriaged [ 10059 ] New: Needs Triage [ 10030 ]
            Mauricio S (Atlassian) made changes -
            Description Original: *Summary*
            - After deleting a user from a Jira/Confluence instance, this user is still showing on the People Directory and clicking on the user to see its profile re

            *Environment*
            - Cloud

            *Steps to Reproduce*
            # Verify a domain and set-up a SAML SSO integration with Atlassian
            # Log in to create a SAML ID with the Atlassian account
            # Verify a new domain and remove the old one
            # Create a new Atlassian account with the new domain
            # Change the user's email in the IdP
            # Log in with the new email

            *Expected Results*
            - The user can log in without problems. The "_login.forbidden.handle-linked-saml-users.update-linked-primary-user-email-failed-400.content_" is not a problem anymore

            *Actual Results*
            - The user can't log in. A message error appears saying: "_Oops, there was an error logging you in. login.forbidden.verify-saml-domains.invalid-email-domain-for-primary-user.content_". For your reference:


            *Workaround*
            - Re-verify the old domain and ask the users to log in with their new account.
            New: *Summary*
            - After deleting a user from a Jira/Confluence instance, this user is still showing on the People Directory. Additionally, if we try to click on the user to see its profile we get an error message saying: "Something went wrong. We keep track of these errors, but feel free to contact us if refreshing doesn’t fix things."

            *Environment*
            - Cloud

            *Steps to Reproduce*
            # Interact with a user to make it appear in the People Directory page
            # Remove the user from the instance
            # Go to the People Direct page again

            *Expected Results*
            - The user won't show in the People Directory page after being removed from the instance

            *Actual Results*
            - The user is still appearing in the People Directory page and if you click on it you will be redirected to a page showing the message: "Something went wrong. We keep track of these errors, but feel free to contact us if refreshing doesn’t fix things."

            *Workaround*
            - Interact with other users to change the ones that appear in the People Directory page.
            Mauricio S (Atlassian) made changes -
            Summary Original: Deleted users keep showing on People Directory New: Deleted users keep showing on People Directory and it's not possible to see its profile
            Mauricio S (Atlassian) made changes -
            Description New: *Summary*
            - After deleting a user from a Jira/Confluence instance, this user is still showing on the People Directory and clicking on the user to see its profile re

            *Environment*
            - Cloud

            *Steps to Reproduce*
            # Verify a domain and set-up a SAML SSO integration with Atlassian
            # Log in to create a SAML ID with the Atlassian account
            # Verify a new domain and remove the old one
            # Create a new Atlassian account with the new domain
            # Change the user's email in the IdP
            # Log in with the new email

            *Expected Results*
            - The user can log in without problems. The "_login.forbidden.handle-linked-saml-users.update-linked-primary-user-email-failed-400.content_" is not a problem anymore

            *Actual Results*
            - The user can't log in. A message error appears saying: "_Oops, there was an error logging you in. login.forbidden.verify-saml-domains.invalid-email-domain-for-primary-user.content_". For your reference:


            *Workaround*
            - Re-verify the old domain and ask the users to log in with their new account.

              briosa Blake Riosa (Inactive)
              msoliz@atlassian.com Mauricio S (Atlassian)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: