EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB489535: Data import from Jira Cloud Connector failed: API removed (410 Gone). Please migrate to /rest/api/3/search/jql.


Community Admin

• Strategy


End users may encounter the error "410 Gone POST https://bancoicbc.atlassian.net/rest/api/2/search" with the message "The requested API has been removed. Please migrate to the /rest/api/3/search/jql API." when attempting to import data using the Jira Cloud connector. This issue occurs because Atlassian has deprecated the /rest/api/2/search and related JQL search and Evaluate expression endpoints after May 1, 2025.

Symptom

End users attempting to import data using the Jira Cloud connector may encounter the following error:

{Jira Project} Error in importing file. Check the file to import. [Retrieving data from data connector failed. Error in importing files. Please check the file to import. Error type: Data Import Error. Fail to fetch data. Please check whether IServer machine can access the data source. HttpResponseException. 410 Gone POST https://bancoicbc.atlassian.net/rest/api/2/search {"errorMessages":["The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046"], "errors":{}}.]

 

Cause

Atlassian has deprecated the /rest/api/2/search and related JQL search and Evaluate expression endpoints as of May 1, 2025, integrations relying on these endpoints will no longer function and need to be updated to use the new /rest/api/3/search/jql API.  More details can be found here.

 

Solution

Upgrade the CommunityConnector.war file to Strategy One Update 5 or a later version.

 

 


Comment

0 comments

Details

Knowledge Article

Published:

September 29, 2025

Last Updated:

September 29, 2025