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
GET /rest/api/3/search
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
POST /rest/api/3/search
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
POST /rest/api/3/search/id
No direct replacement, similar behaviour can be achieved with
POST /rest/api/3/expression/eval → The Jira Cloud platform REST API
POST /rest/api/3/expression/eval
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,
Hi @Limor Segal Shevah - I am not a maintainer of either the jira nor the atlassian-python-api packages, but I do see recent updates to both of those packages from skumar36-atlassian
So you'll need to update to the latest versions of the packages, and in both cases it looks like you'll need to adjust your scripts to use new functions enhanced_search_issues (jira) or enhanced_jql (atlassian-python-api).
It looks like you're new here. Sign in or register to get started.
