How to show username and uid in user search userpicker

[Juan_Jose_Andres_Gerez]

For needs of my JIRA instance I have registered users via LDAP that have different identifiers, since they attack different LDAPs, but they have the same name.

I am entrontrating that when I assign an issue to a user, and I look for it by its name, I see the "duplicate" records. It is really correct, they have two different uids, but I can not see which is the uid of it to assign it to the user Right.
Currently my instance shows the user's name and email, which does not allow me to correctly identify the user.
Is there a way to change the format of the user search so that instead of showing name and email, show name and uid?

[Andy Heinzer]

Hi Juan,

I see that you are using an LDAP server with Jira in a way such that your user accounts appear to be duplicated, and in turn you are looking for a way to differentiate these different unique user accounts.

There is no way that I am aware of that Jira would allow you to clearly identify the user direct that account originates from, at least not from the user picker.  Perhaps it might be possible with a plugin to Jira, but I don't think this is the best approach.

Instead, I'd like to know more about why you have these user accounts duplicated within Jira first.  Atlassian's own documentation on Managing multiple directories, clearly suggests that you should

Avoid duplicate usernames across directories. If you are connecting to more than one user directory, we recommend that you ensure the usernames are unique to one directory. For example, we do not recommend that you have a user jsmith in both 'Directory1' and 'Directory2'. The reason is the potential for confusion, especially if you swap the order of the directories. Changing the directory order can change the user that a given username refers to.

To that end, the way I would prefer to troubleshoot this issue would be to understand why you have these duplicated accounts in Jira, and if possible reduce the number of user directories in Jira to eliminate the duplicate accounts entirely.

I had another recent thread from another user that kept adding the same LDAP user directory to Jira with a different user selector filter because there was a misunderstanding about how application access and permissions could be distributed to those user accounts.  It might help to check out https://community.atlassian.com/t5/Jira-questions/Jira-LDAP-Duplicated-users/qaq-p/1098102 as it feels like it relates to your topic in a similar way.

Regards,

Andy