Details
-
Suggestion
-
Resolution: Fixed
-
None
-
2
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When using the Issue Picker type-ahead, it will repeat the user's last JQL search several times as the user types an issue.
So if the user ran a slow search such as any using "WAS", it creates some pressures on the system. Ideally, WAS/WAS IN performance should be addressed, but this behavior doesn't help:
11 "GET /rest/api/1.0/issues/picker?currentJQL=... 11 "GET /rest/api/1.0/issues/picker?currentJQL=... 11 "GET /rest/api/1.0/issues/picker?currentJQL=... 11 "GET /rest/api/1.0/issues/picker?currentJQL=... 11 "GET /rest/api/1.0/issues/picker?currentJQL=... 11 "GET /rest/api/1.0/issues/picker?currentJQL=...
Reproduction
1. Run a slow JQL search
2. Open an issue
3. Open the Link operation, and start typing an issue key
4. JQL searches are fired in the background