JQL Search endpoints API changes

[Limor Segal Shevah]

Hi,

Do you intend to have a new versions for search JQL changes in jira-python module? if so which jira-python module version will support the following changes in API?

Deprecated Endpoint	New Endpoint
GET /rest/api/3/search → The Jira Cloud platform REST API	https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get
POST /rest/api/3/search → The Jira Cloud platform REST API	https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-post
POST /rest/api/3/search/id → The Jira Cloud platform REST API	No direct replacement, similar behaviour can be achieved with https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-post
POST /rest/api/3/expression/eval → The Jira Cloud platform REST API	https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-jira-expressions#api-rest-api-3-expression-evaluate-post

Also for another question, do you intend in all API changes in the future?

Thank you,

[Saif Shaikh]

API changes, especially with JQL search endpoints, can be both exciting and challenging. They often bring improved capabilities but may require reworking existing integrations. A tip for adapting to these updates is to carefully review the updated API documentation and test queries in a staging environment before deploying to production.

At Axie IT Consulting, we’ve worked extensively with API integrations and query optimizations for various platforms. If you’re looking for support in adapting to these changes or improving your JQL queries for better performance, feel free to explore our services at front end web development services. Happy to collaborate or provide insights

[Limor Segal Shevah]

Thank you Saif for your response, I appreciate your help.

Ofcourse we are doing these too as we did in the past with API changes. Sometimes we use python module and sometimes we are developing alone and working directly with developer API guide. 

Thanks again,

Limor