Hi to all,

JIRA has had this ability for a few releases, from at least 4.1.
Sorry that we did not resolve this issue earlier.

Cheers,
Roy

I just saw this ticket, but it is something that we have been complaining about amongst ourselves for a while now.

Please make it higher than minor... this is not minor in an environment of 2000 users like we have.

Thanks for the patch, Rossato! Just wanted to point out to others that I found userbrowser.jsp in <JIRA_HOME>/atlassian-jira/secure/admin/user/views/ not in <JIRA_HOME>/atlassian-jira/WEB-INF/classes/secure/admin/user/views/
Also, we have a couple thousand users and I found you can search by full name if you go to a screen such as the "Bulk Edit Group Memebers" and click on the user selector widget icon. But this patch makes it easier.

I administer MANY 3rd party products and this is the only one that doesn't let you filter on usernames. Atlassian must have had a pot luck going on that day and the developer wasn't thinking too clearly regarding the purpose of a user browser screen.

Hi,

We have more than 10.000 users. So, the ability to search an user by full name or login or any other attribute related to the user is a major issue for us. Considering that this issue is more than 4-years old and that there is no solution neither a comment from Atlassian so far, we have decided to investigate the source code to check how complex it would be to implement this "minor" feature.

Believe me! We, that are not JIRA developers, have taken less than 2 hours to understand the logic, modify the source code and put it in production! Of course we don't know if it is OK from Atlassian stand point, but it is working for us!

We would appreciate a comment from Atlassian saying if the patch can be used for other users and if they plan to include this patch in future releases.

So ... here is the patch for the JIRA 3.13.2 Enterprise version. It may work with other versions too, but you must test before putting in production mainly if you are using a different version.

1. First, backup your files!
2. Replace the userbrowser.jsp located at <JIRA_HOME>/atlassian-jira/WEB-INF/classes/secure/admin/user/views/ by the attached file.
3. Replace the UserBrowser.class located at <JIRA_HOME>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/admin/user/ by the attached file.
4. Restart your JIRA instance.
5. If it won't work, restore the files.
6. Have fun!

We have over 800 users. If an employee leaves out company or change surname it is very difficult to find it. Please make the priority of this task higher.

Why is this just a MINOR issue???? Aiiyee it's so annoying and frustrated to not able to find user quickly. This reminds me of crippled Outlook application. Please bump up the priority and have a fix soon!!!

Why would these functions (search by username, search by full name) in Confluence but not in JIRA

is really hard to find users!

yep, we have 300 jira users and sometimes the email is not directly mapped to usernames, so it is very hard to find them, cause you need to browse.