REST: The new /rest/api/3/search/jql endpoint is a complete disaster

[p0cket0m]

We were perfectly happy with the existing search endpoint, and yet Atlassian decided to force everyone onto the new search endpoint /rest/api/3/search/jql. The result? A complete mess:

• Pagination is broken. isLast never returns true, nextPageToken chains endlessly, delivering thousands of new and unique tokens, but always loading the first page again and again. Integrations are left in infinite loops.

• Performance is abysmal. Even for a few thousand issues, requests slowly crawl page after page, wasting time and resources. Nobody can run production pipelines like this.

• Stability is gone. Scripts that worked reliably for years with /search are now brittle, complex, and full of hacks just to load basic data.

• Documentation is misleading at best, outright wrong at worst. Developers are left guessing, testing, wasting hours on trial and error.

The bug is known, but why did they close the issue without resolving it? https://jira.atlassian.com/browse/JRACLOUD-94632

Solution:
We did not transition to the new token-pagination endpoints like suggested in Atlassian's email. We now reimplemented the complete interface, using existing Jira Agile API

/rest/agile/1.0/board/{BOARD_ID}/issue

Pagination is working here as expected.

[Marc - Devoteam]

Hi @p0cket0m 

Here in community, most of us are Atlassian users like yourself.

This community is an open public form.

On your concerns, reach out to Atlassian Support or use the feedback option in the application, to provide this feedback.