Hello community,
as the old jql search for issues is deprecating, we are changing our apps calls to the
enhanced JQL search (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get ) and we need to perform searches that might bring 15,000 issues or so.
With the deprecated endpoint, our apps calculated the number of pages and could make a number of requests at the same time, each one to bring a "page" of issues, at a reasonable performance.
However, with the enhanced search endpoints, we are no longer able to make all these calls simultaneously but one by one, picking the nextPageToken.
As each call brings max 100 issues, we need to make 150 requests one after the other, and each response takes about 10 seconds, so to bring all the issues takes 25 minutes, which is unacceptable in terms of performance for our app.
Is there anything we can make differently to make things faster? The deadline for the old endpoints is May 1st, and we are running out of time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.