When are JQL search endpoints /rest/api/2/search and /rest/api/3/search really being removed?

[Sebastien Brion]

According to this changelog entry, the /rest/api/2/search and /rest/api/3/search endpoints will be removed on May 1st, 2025.

Those endpoints are still working, but I'm wondering how much time we really have to get off them. I'm not seeing any other announcement in the changelog.

(This was already asked as a follow-up on this resolved question)

[Sebastien Brion · Accepted solution]

We got this answer from Atlassian Support in a Jira support ticket:

I took a look at our documentation and found the following timeline. Please note, although this is the most up-to-date timeline we have, it can certainly change if anything unexpected happens:

Here is a summary of the timeline:

* Deprecation Period May 1st: Endpoints are officially deprecated, however, they continue to remain functional.

* Transition Period: From May 5, 2025, to July 31, 2025, JSIS will be rolled out under the hood for old APIs, improving performance but introducing eventual consistency.

* Final Shutdown: From August 1, 2025, to October 31, 2025, the deprecated APIs will be progressively shut down, with all traffic blocked by the end of October 2025. Any requests to these endpoints will return errors (e.g., "410 Gone").

[Dan Breyen · Accepted solution]

Hi @Sebastien Brion as we're well past May 1st, I figured it would be worth it if Atlassian Support could assist with getting an answer for you.

Hope that helps.

[Sebastien Brion]

Thanks for the suggestion. We did this and got a response.

[Jimmy Tao]

@Dan Breyen 

Where can we request an exception for more time on a few projects we critically are using. The new search JQL API requires significant work to implement.

[Dan Breyen]

Hi @Jimmy Tao that would be a good question to ask Atlassian Support about.  As a community of users, we wouldn't be able to answer that question for you here.

[David Nickell]

I would say the actual change is starting to be rolled out. 

Approximately 2 days ago the "old" search worked for my site and the shared "ecosystem" site.

Today, it only works for my site.

---

Old Endpoint Format

---

New Endpoint Format

[Sanapala_ Sriman]

Will we be able to get the complete JSON like in the 1st screenshot with the new end point URL i am only getting Id's like 2nd screenshot, Any suggestions? 

[M]

Add query parameter fields to *navigable 
As default is "id" only in /search/jql API.
Old API /search default for fields was *navigable

Source:
New one:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get
vs
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get

Same for v2 endpoints.

[Sanapala_ Sriman]

If I need the total count to loop through all Stories or Epics or Initiative and I don't need the next page token I need the complete list. is there a way I can them with any query params

"total":

[M]

Per 
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get
you can get up to 5000 max assuming you only request id or key field:

maxResults

integer

The maximum number of items to return per page. To manage page size, API may return fewer items per page where a large number of fields or properties are requested. The greatest number of items returned per page is achieved when requesting id or key only. It returns max 5000 issues.

(which makes totally sense - as limits are essentially good idea in IT) 

Assuming you need *navigable - you have to write the logic for looping paging.

Here is the guide how to do it in Python:
https://community.atlassian.com/forums/Jira-articles/How-to-use-the-new-Jira-cloud-issue-search-API/ba-p/3006109

but for other languages GenAI should do it easily.

[Sanapala_ Sriman]

What is the best way to build and pull the Stories, Epics Initiatives and respective Details (comments, etc) into Qlik Sense form Jira Cloud ?