Upcoming Deprecation of Jira Cloud Search APIs

[glewandowski]

Problem trying to solve

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

Possible solution(s)

client.py#search_issues

jira/jira/client.py

Line 3484 in 3a630c5

def search_issues(

Function should be updated so it does call new endpoint /rest/api/3/search/jql and does not expose any deprecated parameters like startAt or validate_query

Alternatives

No response

Additional Context

No response