Our company has a peculiar requirement from the legal team that:

• givenName is the given name of the user on their birth certificate
• sn is the surname of the user on their birth certificate
• displayName / cn is the name they go by day-to-day

So we end up with lots of cases such as "Mark Anderson" who are really "Chris Anderson" or "Steven Smith" who is "Paul Smith". This causes major confusion for our users who are only peripherally aware of the legal requirements, and don't know each other's legal names.

There are other cases where the legal name might have multiple names like "Jean Luc Picard" where the person might go by "Jean Picard". Searching on "Jean Picard" in this case when adding a user to a group or access controls fails, I believe.

The confusion is anywhere that Stash lists users such as the access controls, or group members. It affects search because it is really difficult to find these people.

Please change the behaviour so that when a "display name" is warranted, it will use "displayName" or "cn" (ideally configurable) instead of sandwiching "givenName" and "sn" together.

I'll note that different Atlassian tools work differently here, but most of them in my experience use a "displayName", and Stash is more of the odd man out here. I know this because our other tools - JIRA, Confluence, Bamboo, etc. don't seem to be having this problem. (I'll note that Confluence actually does it both ways... mostly they use "displayName" or "cn", but sometimes, as is the case with personal space titles, they use "givenName sn", and our users also complain about this...)