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

Managed users not tied to an external directory are not being able to change their full name

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • User - Email change
    • None
    • Production

      Issue Summary

      Since our recent profile privacy changes, managed users lost the ability to change their full name on start.atlassian.com while not tied to external directories through SAML, SCIM or G Suite.

      Before the change, users were able to do that, also confirmed by our public documentation about Atlassian account for users:

      If your account is managed by your company, only your admin can:

      • Update the email address for the account
      • Deactivate or delete the account

      Steps to Reproduce

      1. Have an Atlassian organization with your domain verified.
      2. Have a managed user under the same domain.
      3. The user logs in to start.atlassian.com and clicks to Manage Profile, through the main screen or profile picture on the low-left corner.
      4. The user tries to change the full name.

      Expected Results

      The user should be able to edit the field inline and change the full name.

      Actual Results

      The user is prompted that only the organization administrator can do that:

      Notes

      The end users can no longer change their own full names and they do not have visibility of who to contact for this change.

      Workaround

      Reach out to Atlassian support for the contact information of their organization administrators.

            [ID-7040] Managed users not tied to an external directory are not being able to change their full name

            rbecker

            discussed this with jryden that we need the end user to enter this URL in their browser for us to debug what's going on:

            https://api-private.atlassian.com/users/{user_id}/manage?privileges=profile.write

             The above will return us a JSON object that we can use to determine the reason why they are not able to change their name. Currently there's no way we can see what's going on, as we require the user context to authorize the request and nobody can fake the user context.

             

            Mitch Yuwono (Inactive) added a comment - - edited rbecker discussed this with jryden that we need the end user to enter this URL in their browser for us to debug what's going on: https: //api- private .atlassian.com/users/{user_id}/manage?privileges=profile.write  The above will return us a JSON object that we can use to determine the reason why they are not able to change their name. Currently there's no way we can see what's going on, as we require the user context to authorize the request and nobody can fake the user context.  

              ayang@atlassian.com Aneita
              rbecker Rodrigo B.
              Affected customers:
              3 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: