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 article, https://confluence.atlassian.com/pages/viewpage.action?pageId=296094848which 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 have also submitted a JIRA issue regarding this, with a screenshot. https://jira.atlassian.com/browse/CONF-34696
This has been confirmed a bug, and will be corrected when https://jira.atlassian.com/browse/CONF-34696 is closed.
To get around this, you can do it by manually clearing your content indexes:
After that, the user mentions will be in the format of givenname + sn.
So changing the user's display name is still tied to a single LDAP attribute, unless you put in a dummy value at which point it will default to givenName + sn.
However, the re-indexing problem appears to have been corrected in 6.7 with the improved @mentions functionality, and simply re-synchronizing will update all mentions, so the above Jira issue can be closed.
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs