Upcoming Deprecation of Jira Cloud Search APIs

[glewandowski]

What feature do you want to see added?

On October 31, 2024, Atlassian announced the deprecation of four Jira Cloud search APIs. These APIs will be replaced with new, more efficient alternatives through our enhanced JQL service, which are currently available for use. You can read more about these new APIs here.
Effective May 1, 2025, Atlassian will remove the following Jira REST endpoints:

• GET /rest/api/3/search
• POST /rest/api/3/search
• POST /rest/api/3/search/id
• POST /rest/api/3/expression/eval
  We have identified that this library may be used to access the deprecated endpoints in Jira Cloud. Failing to migrate to the new APIs before May 1, 2025, could negatively impact any solutions that depend on this library. By evolving our JQL service, we aim to provide a more reliable, performant, and scalable Jira experience tailored to meet the needs of enterprise customers.
  If you have any questions or require further assistance, please do not hesitate to ask on our developer community forum

Upstream changes

No response

[saurabhraghuvanshii]

can I work on this

[SohamJuneja]

I’ve implemented the changes as suggested, specifically:

Searched for instances of GET /rest/api/3/search, POST /rest/api/3/search, POST /rest/api/3/search/id, and POST /rest/api/3/expression/eval in the codebase.
Checked through relevant parts of the repository to locate any calls or references to these endpoints.
However, I wasn't able to find any instance of these API calls or related code in the repository.

[glewandowski]

I can see the deprecated APIs are used here

jira-plugin/src/main/java/hudson/plugins/jira/JiraRestService.java

Line 227 in 03411e0

public List<Issue> getIssuesFromJqlSearch(String jqlSearch, Integer maxResults) throws TimeoutException {

But I also I see, they use old, non-mantained Jira REST client. I'll check if Atlassian can release new version that doesn't use deprecated APis.