Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-59412

See more available fields for Columns in List View of Issue Navigator without typing

XMLWordPrintable

    • 2
    • 16
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

      1. Create one custom field with a specific name (e.g. "Type")
      2. Create at least 25 other custom fields with any combination of characters, followed by "Type" (e.g. "Example Type")
      3. Go to the Issue Navigator, and be in List View.
      4. 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

      1. Rename the custom field to something else which does not cause this issue in the Column search.
      2. Add this renamed field as a column to the List View in the Issue Navigator
      3. Rename the custom field back to what it originally was

      Filters

      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)

        1. List_old.js
          31 kB
        2. List.js
          31 kB
        3. List.js
          31 kB
        4. List-min_old.js
          16 kB
        5. List-min.js
          16 kB
        6. List-min.js
          16 kB

              Unassigned Unassigned
              kliou Kevin Liou
              Votes:
              42 Vote for this issue
              Watchers:
              39 Start watching this issue

                Created:
                Updated:
                Resolved: