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

Synchronize the full name with the values provided by the givenname or surname, even if one of these fields is empty.

XMLWordPrintable

    • 1

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

      Current functionality:
      User Provisioning will utilize the Display Name attribute to be used as the Full Name on the User’s Atlassian account. ( )On the other hand, SAML Single Sign-on will Just-in-Time update a User’s Atlassian account based on the givenName and Surname Attributes sent as part of the SAML SSO authentication. If a User was synced via User Provisioning with a Full Name created with a Custom Display Name value, it will be overwritten if SAML sends something else

      When a user has only one of these attributes filled (For example, only the givenName is filled and the surname is empty), then the value of the primary email is used to populate the Full name field instead.

       

      The suggestion:

      Sync the Full Name field with the values provided by the givenname or the surname, even if one of these fields is empty.

       

            [ACCESS-1739] Synchronize the full name with the values provided by the givenname or surname, even if one of these fields is empty.

            Dylan made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels Original: guard-s8 New: cll-tf3202505 guard-s8
            Leonardo H made changes -
            Labels New: guard-s8
            SET Analytics Bot made changes -
            Support reference count New: 1
            Mariana Bastos [Atlassian Support] made changes -
            Description Original: *Current functionality:*
            User Provisioning will utilize the Display Name attribute to be used as the Full Name on the User’s Atlassian account. ( )On the other hand, SAML Single Sign-on will Just-in-Time update a User’s Atlassian account based on the _givenName_ and _Surname_ Attributes sent as part of the SAML SSO authentication. If a User was synced via User Provisioning with a Full Name created with a Custom Display Name value, it will be overwritten if SAML sends something else

            When a user has only one of these attributes filled (For example, only the _givenName_ is filled and the _surname_ is empty, then the value of the +_primary email_+ is used to populate the Full name field instead.

             

            *The suggestion:*

            Sync the +Full Name+ field with the values provided by the _givenname_ or the {_}surname{_}, even if one of these fields is empty.

                          		New: *Current functionality:*
            User Provisioning will utilize the Display Name attribute to be used as the Full Name on the User’s Atlassian account. ( )On the other hand, SAML Single Sign-on will Just-in-Time update a User’s Atlassian account based on the _givenName_ and _Surname_ Attributes sent as part of the SAML SSO authentication. If a User was synced via User Provisioning with a Full Name created with a Custom Display Name value, it will be overwritten if SAML sends something else

            When a user has only one of these attributes filled (For example, only the _givenName_ is filled and the _surname_ is empty), then the value of the +_primary email_+ is used to populate the Full name field instead.

             

            *The suggestion:*

            Sync the +Full Name+ field with the values provided by the _givenname_ or the {_}surname{_}, even if one of these fields is empty.

             
            Mariana Bastos [Atlassian Support] created issue -

              Unassigned Unassigned
              336d2be4b97f Mariana Bastos [Atlassian Support]
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: