Filter Id based searches are not preserving the ORDER BY sort order clause

This is a problem both for the Issue Navigator and the JIRA Issues Macro available in Confluence.

Workaround

To work around this issue, call the filter by number and apply the sort at the time of use. Example:

filter = 47420 ORDER BY priority DESC

As reported by a customer:

An Employee created a search filter.
When run it includes the ORDER BY priority DESC.
If you go to the full url of the search string it works as expected, and you can click on the P column to sort by priority. Given the operator in the filter it appears properly as descending.
If within Jira you do a search filter="some sumber"
It displays the tickets, however the priority is not shown in DESC order. There is no way of course to click on it either.
This is causing issues as we use the Jira macro to list jira tickets based on a filter. While prior with wiki mark up we could add operators, this is not possible now.
In this case with the Jira macro it truncates the url to filter="some number"
This is an issue as we want to display the list properly sorted based on the search criteria. We are able to replicate this in Jira, but creating a filter, then doing a search with filter="Some number"

Steps to Reproduce

1. Go to Manage Filters
2. Identify the filterid of any filter
3. Go to the Issue Navigator
   1. In Advanced mode, enter filter=<id>
4. Compare to the results of clicking through to the filter from Manage Filters