My Atlassian connect app is working fine from 2018. Recently one user got an below issue,
Error
The requested API has been removed. Please use the newer, enhanced search-based API instead. Deprecation details are available at https://developer.atlassian.com/changelog/#CHANGE-2046
Based on the deprecation, i used “/rest/api/3/search“ rest api to search the issues by jql. But, it didn’t throw any error for me when i access my app or the rest api either.
The latest recommended rest api “/rest/api/3/search/jql“ is working fine in browsers tab but it throws an error in app.
Why it behaves so? How to handle this?
1 Like
Hello @rajagopal
Are you running your test of your Connect app against the exact same Jira Cloud instance in the exact same geographic region as the user?
Given that Atlassian are rolling out the change across the world, it’s logical to assume that some instances in some regions may not yet have the change applied (It’s not yet applied in my region)
The latest recommended rest api “/rest/api/3/search/jql“ is working fine in browsers tab but it throws an error in app.
What was the actual request made to the new endpoint and what was the error returned?
Hi Sunnyape, thank you for your quick response. It’s strange to experience different behavior based on the regions. Anyway, moved to newer endpoint now.
Previously search endpoint provides results with it’s fields property, now i found the additional parameter to access those which i missed earlier.
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get