REST API search endpoints are slower compared to issue navigator

Still need help?

The Atlassian Community is here for you.

Ask the community

This Knowledge Base article applies equally to both the Atlassian Server and Atlassian Cloud platforms.

This Knowledge Base article was written specifically for Atlassian Data Center applications. The contents of this article do not apply to Server installations or the Atlassian Cloud platform.


When running a JQL search using REST API, the results are returned significantly slower than the issue navigator. 


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:

Please also take note of this known bug :


When performing REST api searches, ensure to specify the fields for example :


If 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.

Last modified on Oct 15, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.