Filter Results gadget does not honor the sorting criteria when there exist more than 3 Order By clauses

Issue Summary

This appears to be a regression of JRACLOUD-21443 in which the filter results gadget will incorrectly display the order of issues if the saved JQL filter it is using happens to have 4 or more Order By clauses within it.

Steps to Reproduce

1. Create a JQL Saved filter such that it has at least 4 Order By clauses in it.  Example JQL queries where I have observed this:

   • sprint is not empty and "Epic Link" is not empty ORDER BY Sprint ASC, status ASC, "Epic Link" ASC, key ASC 

   •  project = ssp ORDER BY priority, status, reporter, key ASC 

2. On a Dashboard, add a new gadget of type Filter Results, select this saved filter from step 1

Expected Results

We expect that the issue navigator in Jira and the gadget will display these issues in the same exact order

Actual Results

It appears that the filter gadget does not honor that 4th order by clause, in this case key ascending.  The results in the gadget behave as if that 'key ASC' doesn't exist at all.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available