REST API search endpoints are slower compared to issue navigator
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
Support for Server* products will end after February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When running a JQL search using REST API, the results are returned significantly slower than the issue navigator.
Cause
By default, if no fields are specified when searching via REST, all fields are returned. The results are quicker from the issue navigator GUI is because not all fields are selected.
We have a suggestion ticket to improve this here:
-
JRASERVER-69676
-
Getting issue details...
STATUS
Please also take note of this known bug :
- JRASERVER-68602 - Getting issue details... STATUS
Workaround
When performing REST api searches, ensure to specify the fields for example :
{base_url}/rest/api/2/search?jql=text%20~%20task\&fields=summary,description,reporter,assigneeIf you have recently updated a plugin and just started facing this issue, tracking down which plugin custom field is causing this issue will also help. You may try disabling a few of those plugins which you recently updated and run the REST API command again to see if there are any difference in the time. If it is indeed faster, you can then enable the plugin one by one until you find the plugin which has the field that is causing the slowness.