Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-905

Provide a web UI to change the managed accounts' public name for organization admins

XMLWordPrintable

    • 91

    • 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.

      Implementation of New Features Policy


      At the moment, we can't set an ETA for this feature to be released, since there's a number of factors that determine how our product team prioritizes new features. Consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.
      You can learn more by reading Implementation of New Features Policy.

      Problem Definition

      An organization admin cannot modify the public name at https://admin.atlassian.com/ while the REST API accepts update requests.

      Suggested Solution

      Add the public name field to the form so that organization admins can update the managed accounts' public name.

      Workaround

      Update the nickname property in PATCH /users/{account_id}/manage/profile.

        1. Screen Shot 2020-07-22 at 14.29.30.png
          Screen Shot 2020-07-22 at 14.29.30.png
          959 kB

            [ACCESS-905] Provide a web UI to change the managed accounts' public name for organization admins

            SET Analytics Bot made changes -
            Support reference count Original: 90 New: 91
            SET Analytics Bot made changes -
            Support reference count Original: 89 New: 90
            SET Analytics Bot made changes -
            Support reference count Original: 88 New: 89
            SET Analytics Bot made changes -
            Support reference count Original: 87 New: 88
            SET Analytics Bot made changes -
            Support reference count Original: 86 New: 87

            Mykenna Cepek added a comment -

            We're preparing for a migration from Jira Data Center to Jira Cloud. And our user names and avatars in Jira Cloud are all over the map. We see:

            • First Last
            • First M Last
            • Last, First
            • Last, First M
            • First L
            • First

            We've confirmed this is not coming from our AD or SSO. While I understand this "User Profile Data" is in the user's Atlassian account, things get tricky when an large organization wants to have a consistent user experience, especially for aspects so basic as name format and avatars/initials.

            We have had "bug reports" during our pre-migration Jira Cloud UAT that avatar initials are wrong (e.g. Last Initial then Middle initial) for some people on their team but not others. And sometimes there's just one letter/initial.

            While it wouldn't be ideal, perhaps there needs to be org-specific names in user profiles, if only for visibility. It wouldn't be editable by the user, since that's what arduous corporate processes are for.

            Mykenna Cepek added a comment - We're preparing for a migration from Jira Data Center to Jira Cloud. And our user names and avatars in Jira Cloud are all over the map. We see: First Last First M Last Last, First Last, First M First L First We've confirmed this is not coming from our AD or SSO. While I understand this "User Profile Data" is in the user's Atlassian account, things get tricky when an large organization wants to have a consistent user experience, especially for aspects so basic as name format and avatars/initials. We have had "bug reports" during our pre-migration Jira Cloud UAT that avatar initials are wrong (e.g. Last Initial then Middle initial) for some people on their team but not others. And sometimes there's just one letter/initial. While it wouldn't be ideal, perhaps there needs to be org-specific names in user profiles, if only for visibility. It wouldn't be editable by the user, since that's what arduous corporate processes are for.
            Sudesh Peram made changes -
            Assignee Original: Sudesh Peram [ e902c0832f88 ] New: Kunwardeep Singh [ 5cd8def7e384 ]
            SET Analytics Bot made changes -
            Support reference count Original: 85 New: 86
            SET Analytics Bot made changes -
            Support reference count Original: 84 New: 85
            SET Analytics Bot made changes -
            Support reference count Original: 83 New: 84

              5cd8def7e384 Kunwardeep Singh
              kyamamoto@atlassian.com K. Yamamoto
              Votes:
              59 Vote for this issue
              Watchers:
              59 Start watching this issue

                Created:
                Updated: