Problem

JQL API requests, and macro's used within confluence, fail when more than 7 OrderBy columns are used in the query. Also without a friendly error messaging stating the error reason.

Suggested Solution

Increase the limit of "Order by" fields for JQL search queries above the existing max of 7

Why This Is Important

Although I can understand the reason behind the Jira API change, our end-users may find it difficult to accept. They have a significant number of existing pages where the JIRA macros (with 7+ "ORDER BY" fields) are now broken. This would require them to manually edit each page and macro to implement a workaround.

Furthermore, since these are native Confluence macros, users expect them to function seamlessly. A change in the Jira API shouldn't retroactively break established, native features in Confluence.

Workaround

There is currently no workaround available to use more than 7 columns in the OrderBy clause.