Sunset schedule for Issue API #CHANGE-2046

[AppFlow]

Hi All,

As per the change logs https://developer.atlassian.com/changelog/#CHANGE-2046 the issue  search API v2 is deprecated and will be sunset by 30 sept 2025 progressively  starting from May 1 2024 as per the change log information and User are supposed to migrate to v3 JQL 

we would like to know how the sunset is scheduled , will the API be sunset completely at one time ?or region specific sunset? or based on the Account

some users faced the error "The request failed because the service Source Jira Cloud returned the following error: Details: "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.". Status code 410 (Gone)"and for some user v2 search API is working ,Request to share the schedule for sunset v2 search API   

[Trisha Griffis]

Atlassian has deprecated the v2 Jira Issue Search API (endpoints like /rest/api/2/search and /rest/api/3/search) and instructed developers to migrate to the enhanced v3 JQL API (/rest/api/3/search/jql).  

• Deprecation & Sunset Timeline
  • May 1, 2025: The initial deprecation date. Atlassian indicated removal of v2/v3 search endpoints would begin. 
  • August 1, 2025: According to ScriptRunner’s release notes, these endpoints are officially scheduled for sunset and removal. 

Why Some Users Still See v2 Working (While Others Get 410 Gone)

• Progressive rollout by region some Jira Cloud instances still support v2 endpoints. Others have already switched to newer APIs. 
• If a v2 request returns a 410 Gone, it means that instance has deprecated it, either regionally or based on Atlassian’s phased rollout.

Response provided by Jer-nee Consulting, an Atlassian Gold Solutions Partner.

[AppFlow]

Thank you  Trisha Griffis for response , Can we have more insights on rollout by region so that we can inform customers of specific region that there is change and rollout is going to take place and provide the new API endpoint to customer whose instance is rollout