Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP 410 Gone.

sergey_mikhlyuk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2025

Our customers began facing issue while syncing data from Jira cloud instances 

HTTP 410 Gone. Error messages: 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.

We are in process of migrating our requests to new endpoints, but haven't finished it yet. Can you prolong the work of legacy endpoints? 

 https://community.atlassian.com/forums/Jira-articles/Avoiding-Pitfalls-A-Guide-to-Smooth-Migration-to-Enhanced-JQL/ba-p/2985433 

1 answer

0 votes
Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2025

Can you prolong the work of legacy endpoints?

Are you really asking someone, somewhere at Atlassian to halt the entire, world-wide roll-out of the deprecation of those API endpoints, just for you?

C'mon @sergey_mikhlyuk, be serious. Atlassian warned everyone 10 MONTHS AGO that those endpoints would be deprecated in May 2025 and to immediately start planning to make the change required. They then gave ANOTHER 3 MONTHS grace period and deferred that deprecation process to August 2025.

If you or your company didn't take advantage of all that time to make the change, then, IMHO, then it's not really Atlassian's problem to fix the situation you now find yourself in.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events