-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upcoming Deprecation of Jira Cloud Search APIs #636
Comments
can I work on this |
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. |
I can see the deprecated APIs are used here
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. |
Hello Everyone We're pleased to announce the release of Jira-Rest-Java-Client to 6.0.2 . This release includes new APIs for Jira Cloud, designed to replace the deprecated searchJql method. These enhanced APIs offer improved flexibility and control for your search operations. New APIs Overview:
|
@SohamJuneja if you are still able to work on this, feel free to assign the issue to yourself and create a Pull Request when ready. You can pull the dependency updates from dependabot's PR in order to have jira-rest-java-client-core already updated to the 6.0.2 version mentioned above. |
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:
/rest/api/3/search
/rest/api/3/search
/rest/api/3/search/id
/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
The text was updated successfully, but these errors were encountered: