-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
6.3.1, 6.4.13, 7.3.3, 7.7.0, 7.0.0, 7.6.4, 7.12.3, 8.13.3, 8.13.9, 8.18.2, 8.20.11
-
6.03
-
56
-
Severity 3 - Minor
-
175
-
Unable to select all options in Issue Navigator screen
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Issue Summary
When using the drop-down menus in the issue navigator screen, users receive the following prompt: 'X more options. Continue typing to refine further.' This shows up in multiple search fields and can prevent users from finding the option they are looking for if they are unsure of the exact name of that value. It can also cause some values to become un-selectable.
For example, when using List View of Issue Navigator, the user has the ability to select fields to add as Columns to the list. The Columns drop down selector can only display 25 fields at any time. In order to see more, the user is prompted with a message as follows: ## more options. Continue typing to refine further.
In the circumstance where a user is trying to search for a value (e.g. "Type"), but the environment has more than 25 fields (including Custom Fields) which have the word "Type" as part of the value, the user may not be able to find "Type" in the list, yet, they cannot refine further by adding more characters; they are only looking for "Type".
This impacts users with a large number of custom fields in their environment, who might stumble into this issue.
Steps to Reproduce
In any other field, the search needs to be refined further to select certain values. This is not the cause for other fields, like the inline user picker in the issue view which displays all options. There are two existing feature requests for this issue:
The value not being selectable can be reproduced in the list view:
- Create one custom field with a specific name (e.g. "Type")
- Create at least 25 other custom fields with any combination of characters, followed by "Type" (e.g. "Example Type")
- Go to the Issue Navigator, and be in List View.
- Click the Columns dropdown, and search for "Type"
Expected Results
The user should be able to select "Type". This could be accomplished by allowing the user to expand the search results without typing (e.g. Click to refine further)
Actual Results
The user is prompted to continue typing to refine further. Any further typing beyond "Type" will result in a non-match for the value "Type", making it impossible to select this value.
Workaround 1
- Rename the custom field to something else which does not cause this issue in the Column search.
- Add this renamed field as a column to the List View in the Issue Navigator
- Rename the custom field back to what it originally was
Workaround 2
Increase the number of fields displayed in the control from the default 25.
Note, that this only helps if the number of status-named fields is not significantly higher than 25, where increasing the threshold will allow you to easily filter through all status-named fields without cutting off.
- Modify the file <JIRA_INSTALL_DIR>/atlassian-jira/includes/ajs/list/List.js as below (after backing up the original file)
find the line below:var maxResult = this.maxInlineResultsDisplayed;
and modify it as below, for example:
var maxResult = 40;Here 40 is the new max length of the list, instead of 25. If this is not enough you may increase it further, but too large values can cause other issues related to display, so better to keep this as low as possible.
- Rename List-min.js file to List-min.js.hide.
- Restart Jira, clear the browser cache, and test if you can reach the desired field.
Note that if you update Jira, this procedure will have to be applied again on each node.
Workaround 3
Select the required field via developer tools manipulations in the browser. You can manually locate the required input control for the field from the page source code, and enable it by following these steps. In this case, we will do this with the "Status" field:
- Perform an issue query or click "View all issues and filters" to cause a list of issues to be displayed.
- Click on the "Columns" dropdown.
- Scroll to the bottom of the list.
- Right-click on the text "Continue typing to refine further". (You can actually right-click anywhere in the Columns chooser, but this puts you close to the tag you're going to be looking for in step 6.)
- Select "Inspect" (on Chrome). This should open a browser development window to the right where you can inspect and modify the page's HTML.
- In the "Elements" window at the top of the inspection area (on Chrome), scroll down until you see an element titled
<select id="user-column-sparkler"...>. - Expand "user-column-sparkler".
- Expand "optgroup label" within it.
- Scroll down until you find the node <option title="Status" value="status">Status</option> (It may be necessary to click "Show all nodes" to see it.)
- Right-click on that node and select "Add attribute". Type: selected="selected". The node should now read:
<option title="Status" value="status" selected="selected">Status</option> - Click "Done" back in the column chooser widget.
- The "Status" column should now appear in your issues list. It should not be necessary to repeat this.
- duplicates
-
JRASERVER-69018 Unable to search 'status' column in issue navigator when I have many custom fields include name 'status'
- Closed
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
- is related to
-
- Closed
- relates to
-
-
- Closed
-
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
[JRASERVER-59412] See more available fields for Columns in Issue Navigator without typing
This is a huge pain - Jira default fields or fields with ONLY the text that matches should display as a priority. Curious of timeline for this update.
Great @Olga Springer.
However just wanted to know how difficult it is to just provide a scroller so user can scroll and select whatever is needed?
Though, yes "Exact Match" at top shall still be there.
Dear Jira users,
We are glad to announce that this issue will be addressed in one of the incoming releases. As you had proposed, we changed the mechanism to prioritise exact matches to the top of the list. For the Columns picker in Issue Navigator, the exact matches of what you search will be prioritized and put at the top of the drop-down list. That will allow you to select any desired field as a column in the List View mode in Issue Navigator.
Thank you for the feedback!
Olga Springer
Product Manager,
Jira Data Center
Can we please get this resolved? Having to teach HTML to each (non-technical) individual complaining about this issue is getting difficult.
Please please please, sort exact matches to the top of the list and this problem will be solved in half a day.
Work-around provided by local Jira management team in my company has asked for fiddling with the HTML code using inspect and get the job done and there are 10 steps in total to get the work done. Not sure if this is the level of quality we expect from an Enterprise product. Please do let us know when will this get resolved.
Please fix, this is absurd that you can't select the field you need to create a report! Seems like a no brainer fix.
Broken UI should not be low priority.
This is not merely a misplaced button / annoyance; the UI is actively preventing our users from using the tool.
GATHERING IMPACT (for 6 years?)
We cannot add the "status" column for our filters. We cannot see what tickets are open, in progress, or done.
^ Look at how many people have the same problem.
Please just show the exact (case insensitive) text match first.
Please prioritize and fix.
The workarounds listed did not work for me or seemed impractical so I developed my own. I am adding it here in case it could be useful for someone else :
- Add a translation for the field in a language you do not use normally (I used German)
- The translation itself does not matter as long as you can easily find it (For our field named "Type" I used the translation "TypeZ")
- Change your profile language to that language
- Add the field to your search columns (it should be easy to find if you chose the translation well in step 1)
- Change you profile back to your preferred language.
The good thing with this is that the translation remains in place. So next time you need to add this field as a column, only the last three steps are required.
Years later and still with the same error. @Atlassian, please, I think is time to resolve this bug.
Let's not over think this.
As noted in the workarounds, the fields we need are there in the HTML, we just need an easy way to see them.
Simply change the "X more options. Continue typing to refine further." text to a link that says (something like) "X more options. Show all."
You can tack "Or continue typing to refine further" on the end, if you want.
We are having issues with the "Status" field.
One recommendation would be to at least have the "system" customfields popping up first.
We also face this issue and raise the ticket "PSSRV-5829 Can't add standard "Status" field to issue navigator"
vote this issue to be fixed in next version release.
this was impacted to v. 8.4 up to 8.14
This is not a minor impact. I cannot show the status column in my JQL query. Status is a pretty fundamental field.
As others have suggested, if you type the word status in the field search, "status" should be at the top. It can't be that difficult to implement.
Thanks
If you've already typed the full Field name (e.g., "Status") and it's still too far down the list to see, there should be an option to select "Exact Match" to find a specific field by its full name. Alternately, the "type to search" function could automatically move any exact matches to the top of the list, so that typing "Status" would always return that field at the top.
This problem has a very big impact. it impact thousands of users in our organization.
It has been logged 5 years ago.
Why isn't it considered/fixed yet?
Thanks,
Valerie.
This is incredibly frustrating. It impacts my daily work - I export all columns to excel (300+) and have to tailor my reports there. This should be such an easy fix.
This issue could be fixed by ordering the list with full match first.
Hi Antonio,
The fix is not working for us even after making changes in List.js and List-min.js
files.
Thanks
TOBY ROBERTS
added a comment - I too am having this problem and would appreciate a workaround as I'm not able to change custom field names. Is there a way to just get the column filter drop down box to just scroll through all results? Or maybe each custom field should have an ID that can be entered instead of just finding titles by name?
TOBY ROBERTS
added a comment - I too am having this problem and would appreciate a workaround as I'm not able to change custom field names. Is there a way to just get the column filter drop down box to just scroll through all results? Or maybe each custom field should have an ID that can be entered instead of just finding titles by name? 
Norman Heath
added a comment - This is a bad problem for us. We have a lot of custom fields. There is no way to add our custom fields to a list. No we can't reboot every time we need to add another field to a list. Potentially thousands of users would be affected.
Norman Heath
added a comment - This is a bad problem for us. We have a lot of custom fields. There is no way to add our custom fields to a list. No we can't reboot every time we need to add another field to a list. Potentially thousands of users would be affected. 
Vickie Vogt-OMalley
added a comment - Do you have to reboot the server after making the changes to the list and list-min files for the changes to take effect?
Vickie Vogt-OMalley
added a comment - Do you have to reboot the server after making the changes to the list and list-min files for the changes to take effect? 
Randy Wilson
added a comment - For users without admin privilege to rename fields, a workaround is highly desirable.
Randy Wilson
added a comment - For users without admin privilege to rename fields, a workaround is highly desirable. Hi, Its important for us, as we have lots of custom fields and "Status" field is not visible while trying to add it in JIRA columns for filter.
The renaming workaround does not work here
I have modified the file "List.js" in order to fix this problem.
What I have done is:
- Add a new variable:
var suggestionsContainers = ["user-column-sparkler-suggestions","filter-column-sparkler-suggestions","system-column-sparkler-suggestions"];
This variable is used to check if the container adding suggestions comes from the column's dropdown button.
- Change:
if (i < maxResult || forceAllResults) {
with this:
if (i < maxResult || forceAllResults || suggestionsContainers.indexOf(this.$container.attr('id'))>-1) {
This fix the error listing all fields that match the entered text, not only the first 25 options.
Tested on JIRA v7.1.1.
The file path is:
Atlassian\JIRA\atlassian-jira\includes\ajs\list
Must make the same change in List-min.js.
I have attached the files:
Old files if anyone wants to compare both.
This should not be a suggestion but a bug.
This also affects JIRA version 7.1.1
This is critical for us because it prevents our users to add some columns to the list.
Workaround: do we have to rename the custom field every time a user wants to add it as a column? 
Im using the same to add Group to a filter. The group name is so that I cannot type further when trying to find it. I thought that changing the group name would solve it (to something like xxxxx Group), but I cannot change groupname, only description.
I suggest a solution easy to implement for this issue: sort the result of the filter in ascending order by length. This is enough to have always on top the exact match, even when a field with a short name si searched and such a name is part of too many other field names!