Based on web browser address bar character limits, a long JQL search that results in a URL over 2000 characters causes inconsistent behavior in different web browsers

https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

Actual results

The actual results vary based on the browser. Generally, these are errors logged to a user through the UI or a console that accompany lack of the search results.

Expected results

The user is either presented with the valid search results and the usual state of the UI or is at least made aware of the JQL query affecting the URL and exceeding the limitations of modern browsers. Most likely, a workaround option is  offered to the user in the later case.

Workaround

Save the long JQL search query as a filter and use its name in a new search query. The new query would look like this

filter = <name of a filter containing the long JQL>

Notes

The bug was initially closed as a duplicate of JRASERVER-28494. After further investigation it became clear that the later issue did not cover the broader context of this flaw hence this one was reopened. 

The URL length limits are not imposed by the Jira itself. Nevertheless, with those limitations existing Jira features should avoid generating URLs that exceed them.