-
Suggestion
-
Resolution: Fixed
-
2
-
16
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Summary
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
- 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 either:
- Changing the search logic to order results starting with the search criteria at the top
- 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
- 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
Filters
- Using PUT - Add Filter Columns endpoint, it is possible to set the columns of a filter you own.
Below, is an example of how this request can be executed using cURL. In this example, the updated filter would have the columns Issue Key, Summary, Assignee, and Status set
curl -D- -u <emailAddress>:<apiToken> -X PUT -d columns=issuekey -d columns=summary -d columns=assignee -d columns=status https://<instance>.atlassian.net/rest/api/3/filter/{filterId}/columns
- For custom fields, specify its IDs in the format customfield_{id} (i.e. customfield_10000)
- is duplicated by
-
JRACLOUD-77382 Only 25 results are returned when adding columns to filters
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
- relates to
-
- Gathering Interest
[JRACLOUD-59412] See more available fields for Columns in List View of Issue Navigator without typing
I am having the same issue with field "Status", we have added many custom fields that contain the word "Status" and I cannot get to the true Jira "Status" field since the list is limited to 25, this is clearly a bug and should be addressed, either expand the list to something like 50, or the perfect fix would be to adding scrolling 25 items a time, so in essence there is no limit.
Also having this issue with 'Status' field. It makes a 1 min update to add this a 1/2 hr exercise as I've needed to start the filter from scratch each time. Infuriating and such a basic feature that's needed. Please fix Atlassian!
I'm a user at a very large organization and have this problem due to the large number of custom fields that have "status" in the name. Since the core "Status" field is listed after the many custom fields "xyz status" and "abc status", it is not possible to select "Status" in the column chooser. The work arounds do NOT work and I'm unable to view my backlog by status. This is super basic functionality that I'm prevented from using. Please fix this.
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.
Hi All,
This has been fixed with the release of New Issue Navigator / Issue Search experience
Thanks
Daniel