Anusha Rutnam added a comment - 12/May/2023 9:12 AM Atlassian Update - May 2023 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

PaulC added a comment - 23/Jan/2013 6:19 PM Hi, I believe the issue is not resolved yet because there still needs to be an "option" for the administrator to be able to choose between the original Full Assignee listing, or the one where you have to start typing before you can select anything. Ideally this choice should also be allowed to be made on a Field by Field basis. There are lots of projects with control over who appears as an assignable user, (or those with simply smaller teams) and in those cases it is not very efficient at all to have to start typing something just when the user list is small. There are also projects that are set up to use all users and in those cases it can make sense to start typing to search. But, it all depends on the users using the system - and i would really like for us to have the choice regarding how to present this field, natively via the front end administration, than to lose an "existing feature" which worked well for lots of users. New features should be Added to jira, as options for those who wish to use them, 'not' as total replacements. That is my humble opinion anyway, formed over several years as a user, as an admin, and when interacting and discussing with several hundred users.

Kavian Moradhassel added a comment - 07/Mar/2012 1:30 PM This appears to have been resolved in JIRA 5.0, with the new Ajax interface for the Assignee field. Is there any reason that this issue hasn't been Resolved?

Brian Mills added a comment - 07/Mar/2012 3:36 AM Currently we have a few JIRA projects with 500+ users. A drop down list makes the interface slower, and is really really bad for useability.

Jon Sword added a comment - 07/Sep/2011 11:22 AM We are preparing to deploy a large JIRA instance and could have thousands of users listed in the assignee drop down. This causes performance issues when loading the page and is not very user friendly. The alternative is we segregate users into hundreds of project groupings - which produces a group management issue and inhibits productivity. The solutions suggested above are not an acceptable workaround as it needs to be re-invented every time Atlassian changes something behind the scenes. Please make this issue a priority.

Jordan Koppole added a comment - 27/Jan/2011 3:00 AM Carl-Johan Wik, Which is the version of JIRA you are working on?

cjwik added a comment - 26/Jan/2011 10:13 AM This is also staring to be an issue for us. Please review this asp if possible.

Kavian Moradhassel added a comment - 11/Aug/2010 8:32 PM This would be quite an important addition for our deployment of JIRA. We're currently in user trials and the feedback we're getting on the Assignee field is not good. We have a large number of assignable users in our projects, and the drop-down list is extremely non-user-friendly.

Jordan Koppole added a comment - 08/Dec/2009 9:32 AM Hello Guys, For JIRA 4.0 I got a this working by tweaking the following 3 files. atlassian-jira/WEB-INF/classes/templates/jira/issue/field/assignee-edit.vm atlassian-jira/includes/panels/issue/assignee.jsp atlassian-jira/secure/views/createissue-details.jsp The file atlassian-jira/WEB-INF/classes/templates/jira/issue/field/assignee-edit.vm holds the control that is to be displayed where assignee is editable. This file requires a complete change. Following is the assignee-edit.vm I have used. #controlHeader ($action $field.id $i18n.getText($field.nameKey) $fieldLayoutItem.required $displayParameters.get( 'noHeader' )) <div class= "ajax_autocomplete" id= "${field.id}_container" > <input type= "text" name= "$field.id" id= "$field.id" value= "$textutils.htmlEncode($!assignee)" style= "width: 30%;" > <fieldset rel= "$field.id" class= "hidden user-picker-params" > <input type= "hidden" id= "fieldName" value= "$field.id" > <input type= "hidden" id= "multiSelect" value= " false " > <input type= "hidden" id= "userPickerEnabled" value= " true " > </fieldset> <a class= "popup-trigger" href= "#" ><img title= "$i18n.getText( 'user.picker.select.user' )" name= "reporterImage" src= "${req.getContextPath()}/images/icons/filter_public.gif" hspace=0 height=16 width=16 border=0 align=absmiddle alt="" /></a> <div id= "${field.id}_results" class= "ajax_results" ></div><font size= "1" >${i18n.getText( 'user.picker.ajax.desc' )}</font> </div> #controlFooter ($action $fieldLayoutItem.getFieldDescription() $displayParameters.get( 'noHeader' )) In the file atlassian-jira/includes/panels/issue/assignee.jsp you need to include the autocomplete js and css that is used and also the script for the popup to select it using the userselect control. The modified assignee.jsp is as follows <%@ taglib uri= "webwork" prefix= "webwork" %> <%@ taglib uri= "webwork" prefix= "ui" %> <%@ taglib uri= "sitemesh-page" prefix= "page" %> <%@ page import = "com.atlassian.jira.ComponentManager" %> <%@ page import = "com.atlassian.plugin.webresource.WebResourceManager" %> <% WebResourceManager webResourceManager = ComponentManager.getInstance().getWebResourceManager(); webResourceManager.requireResource( "jira.webresources:autocomplete" ); %> <%-- This include puts the assignee FieldConfiguration on the stack as it is needed there --%> <webwork:property value= "/field( 'assignee' )" > <webwork: if test= "/hasProjectPermission( 'assignissues' , /project) == true " > <script language= "javascript" > function openWindow(element){ var vWinUsers = window.open( '<%=request.getContextPath()%>/secure/popups/UserPickerBrowser.jspa?formName=jiraform&element=' + element, 'UserPicker' , 'status=yes,resizable=yes,top=100,left=200,width=580,height=750,scrollbars=yes' ); vWinUsers.opener = self; vWinUsers.focus(); }; } </script> <ui:component label= "text(./nameKey)" name= "id" template= "userselect.jsp" > <ui:param name= " 'formname' " value= " 'jiraform' " /> <ui:param name= " 'imagename' " value= " 'reporterImage' " /> <ui:param name= " 'imagesrc' " ><%=request.getContextPath()%>/images/icons/filter_public.gif</ui:param> <ui:param name= " 'imagefunction' " >openWindow( 'assignee' )</ui:param> <ui:param name= " 'style' " >width: 30%;</ui:param> <ui:param name= " 'description' " > <webwork:property value= "fieldDescription" escape= " false " /> </ui:param> </ui:component> </webwork: if > </webwork:property> In the file atlassian-jira/secure/views/createissue-details.jsp need to include the javascripts. just add the following lines to the existing file <%@ taglib uri= "sitemesh-page" prefix= "page" %> <%@ page import = "com.atlassian.jira.ComponentManager" %> <%@ page import = "com.atlassian.plugin.webresource.WebResourceManager" %> and before the </head> tag <% WebResourceManager webResourceManager = ComponentManager.getInstance().getWebResourceManager(); webResourceManager.requireResource( "jira.webresources:autocomplete" ); %> And now reboot your sever If some one is using this solution please let me know if missed including javascript in some files. I understand that which ever pages that this control is used the javascript needs to be included. Also let me know if I am missing something here.

Jordan Koppole added a comment - 04/Dec/2009 8:51 AM Jordan Dea-Mattson, The above solution didn't work for me. Can you please point me what needs to be done. From your forum post I got that you have already solved this. Regards Jordan