Description

When adding fields as columns to be displayed for a filter, only 25 results are returned. In a situation where there are more than 25 results that match the string provided in the search, the desired result may not be returned.

How to reproduce

1. Create multiple custom fields that contain the same word
   • In the test performed, more than 25 custom fields had the word Status in their name
2. Open a filter in the List view
3. Click Columns
4. Search for the field you're looking to add

Expected result

• It would be expected that at least the field that matched exactly the string provided would be returned

Actual result

• Only 25 results are returned, but not necessarily the one you're expecting to see. Because there is no pagination, the desired result may not be reachable
  
• In the example above, there were more than 25 custom fields named <something> Status. The field to be added was the system field Status, but because of this behavior it was not possible to add it as a column, as it is not returned by the search.

Workaround:

• Using PUT - Add Filter Columns endpoint, it is possible to set the columns of a filter you own.

Below, 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)