It appears the way User Mentions are displayed is driven off of the "User Display Name Attribute" in the User Directory Configuration, which we have set to "displayName" in AD. Our displayName attribute is in the format of "Lastname, Firstname" which doesn't look very nice when doing user mentions. And at this point, we can't change the format of our AD attribute.

      So I followed this Atlassian article which describes how you can change your User Directory config to make Confluence instead use "givenname + sn" for displaying user's names (by putting in a bogus attribute). I did that, resync'd the directory with AD, and restarted Confluence and all the user's Profile pages now show a nice "Firstname Lastname" for their Full Name, which is great. But...

      When I go to do a user mention with "@", they still show up and auto-complete using the old "Lastname, Firstname" format. How do we get User Mention's to reflect an LDAP user's new Full Name?

      Note: If I create a LOCAL Confluence user, and change his 'Full Name' (and clear the User Properties cache), it's friendly name in the User Mention reflects the change correctly. Just doesn't seem to work with LDAP users.

      I asked this on Answers, but haven't gotten an answer and I think it could be a bug. https://answers.atlassian.com/questions/329713/change-user-mention-display-name

            [CONFSERVER-34696] Can't change user mention display values

            closed issue

            Deleted Account (Inactive) added a comment - closed issue

            David Hergert (PAYX) added a comment - - edited

            I am not sure, we have not had the need to do it in Jira because we are ok with the "lastname, firstname" format there.

            We just upgraded to 6.8.1, and I changed the "User Display Name Attribute" to a different attribute in AD and re-synchronized my directory, and all pages in Confluence updated with the new format and the editor also reflected the change.  

            So it appears this was corrected in version 6.7 (https://jira.atlassian.com/browse/CONFSERVER-34701).  This issue can be closed, associated with 6.7.  Thanks.

            David Hergert (PAYX) added a comment - - edited I am not sure, we have not had the need to do it in Jira because we are ok with the "lastname, firstname" format there. We just upgraded to 6.8.1, and I changed the "User Display Name Attribute" to a different attribute in AD and re-synchronized my directory, and all pages in Confluence updated with the new format and the editor also reflected the change.   So it appears this was corrected in version 6.7 ( https://jira.atlassian.com/browse/CONFSERVER-34701 ).  This issue can be closed, associated with 6.7.  Thanks.

            Hello dhergert1, can this also be accomplished with JIRA?

            Richard Kerkhoven added a comment - Hello dhergert1 , can this also be accomplished with JIRA?

            To get around this, you can do it doing the following:

            After that, the user mentions will be in the format of givenname + sn.

            David Hergert (PAYX) added a comment - To get around this, you can do it doing the following: Follow the article referenced above LDAP: Changing the User Display Name Attribute to use the default givenname + sn and set the displayName attribute in your User Directory configuration to something fake like "bogusValue" Follow the instructions to Rebuild the Content Indices from Scratch , deleting your index files and then kick off a manual content re-index Give it a few hours (depending on your instance) to repopulate the index After that, the user mentions will be in the format of givenname + sn.

            Hi dhergert1

            Yes this has been confirmed as an issue so this is now on our backlog awaiting someone to work on a fix. Right now we have a number of higher priority issues that we need to address but as soon as we have any more information on this we'll update this ticket with details.

            Regards
            Steve Haffenden
            Confluence Bugmaster
            Atlassian

            Steve Haffenden (Inactive) added a comment - Hi dhergert1 Yes this has been confirmed as an issue so this is now on our backlog awaiting someone to work on a fix. Right now we have a number of higher priority issues that we need to address but as soon as we have any more information on this we'll update this ticket with details. Regards Steve Haffenden Confluence Bugmaster Atlassian

            Hey Atlassian (Steve) - So has this been confirmed and is seen as an issue?

            David Hergert (PAYX) added a comment - Hey Atlassian (Steve) - So has this been confirmed and is seen as an issue?

              Unassigned Unassigned
              eee3c10257fb David Hergert (PAYX)
              Affected customers:
              12 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated: