-
Bug
-
Resolution: Answered
-
Low
-
None
-
7.1.0, 7.2.0, 7.6.4
-
7.01
-
24
-
Severity 3 - Minor
-
18
-
Summary
JIRA XML API takes a long time to return XML data (JQL search result).
There are some integrations (Confluence gadgets ie) that utilize Jira XML API to search and retrieve issues from a filter:
The same JQL query based on a defined filter:
- takes around 30 seconds to gather data via XML API
- takes less than a few seconds via Jira UI.
Observable slowness is not related to enabled add-ons in Jira. Issue is not related to JQL complexity, however it's connected to custom fields usage in the query.
The slowness is related to XML API only, not the JQL itself.
Environment
Jira > 7.0 versions.
Steps to Reproduce
Execute a JQL query that contains any custom field via Jira XML API (searchRequest method):
Expected Results
Execution time is equal (or is close) to the execution time of JQL through web UI.
Actual Results
Execution time is significantly worse than the same JQL through web UI.
Notes
Any integration with Jira XML API is affected (including Atlassian products)
Workaround
No workaround found.
- is caused by
-
CONFSERVER-56017 Regression - JIRA Issues Macro fetching unnecessary fields from JIRA
- Closed
- relates to
-
JRASERVER-68602 Development field causes slower REST search performance
- Gathering Impact
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- was cloned as
-
PSR-193 Loading...