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

[jeffgeorge]

Hi friends, is anybody actively working on this? Starting to get a little concerned as the deadline is rapidly approaching. Losing the ability to search for issues would be a pretty huge blow to how useful this library is.

[wblondel]

This is indeed very concerning. I will try to work on it during the weekends, but I have limited free time.
It would be better if someone else made a PR.

[skumar36-atlassian]

Hello everyone
I am from Atlassian and I have started working on it and will raise a PR once the development is complete.

CC @jeffgeorge @glewandowski @wblondel

[skumar36-atlassian]

Hello @jeffgeorge , @wblondel ,@adehad, @ssbarnea

I have raised a PR for this change: #2326, can you please review. Also as this is my first contribution to this repo, please let me know what all rituals I should follow to meet this repository requirement.

[skumar36-atlassian]

@gonchik can you help in merging/releasing this PR as well?

[wblondel]

PR was pushed to main. I hope it will be part of a release soon.

[studioj]

trials can be run already via pip install git+https://github.com/pycontribs/jira

[lishoujun]

From this week, I find two search exception during search people and create issue from an old stable service.

text: JiraError HTTP None
text: No matching user found for: xxx@domain.com

2. {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}

I guess jira cloud try to warn me to notify this change ?

[ns-ccanevit]

Is there a requirement for Python 3.10 or higher? What about previous versions?

[skumar36-atlassian]

hey @studioj when can we release the change?

[jibraniqbal666]

We are very near to the deadline the Jira will remove these APIs in 1st of May, Can we please release the newer version? @studioj Thanks

[glenn-sq]

[skumar36-atlassian]

hey @studioj are you blocked somewhere?

[studioj]

I don't have any rights to help out with the releasing...
I'm sorry...
I see @adehad and @ssbarnea did some improvements to the GHA ... But I think we're not there yet.