-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Medium
-
None
-
Affects Version/s: 5.2.11, 6.1.1
-
Component/s: Navigation - View results
-
5.02
A user complained that he could not open any issue yet could navigate through other JIRA pages.
Upon investigation we found out that the user once tried to run a JQL query that was too complex and took ~40 minutes to complete.
He abandoned the query at some point but it got saved in the "Issues > Unsaved filter" menu item.
When the user tried to open any issue after that the query would be sent to JIRA server and the page would not open until the query finished.
We fixed the immediate problem by removing the last unsaved query (entered an empty query in the JQL field) but the potential issue still exists.
Is it possible to a) prevent long running queries from execution (e.g. set a time out on the server side); and b) not to execute any saved/unsaved filters when issues are viewed? Is this configurable or requires JIRA code change?
Thank you
Nikolay Borodachev
- is duplicated by
-
JRASERVER-36206 When i ask for an issue, JIRA refresh unsaved filter. Performance problems
-
- Closed
-
- was cloned as
-
JDEV-29447 Loading...