bvignalVPG opened a new issue, #8647:
URL: https://github.com/apache/incubator-devlake/issues/8647

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Hello, 
   
   When i wanted to create a new blueprint, using JIRA, i had the following 
error : 
   
   subtask collectEpics ended unexpectedly Wraps: (2) Retry exceeded 3 times 
calling api/2/search. The last error was: Http DoAsync error calling 
[method:GET path:api/2/search query:map[expand:[changelog] jql:[issue in 
(GITHUB-1111,GITHUB-2222,GITHUB-3333) and updated >= '2025/05/24 00:00' ORDER 
BY created ASC] maxResults:[100] startAt:[0]]]. Response: 
{"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":{}} (410) 
Error types: (1) *hintdetail.withDetail (2) *errors.errorString
   
   
   I am on JIRA Cloud enterprise.
   I installed DevLake using the helm chart in latest wich is devlake 
v1.0-beta1@60faf14
   
   ### What do you expect to happen
   
   Miration JIRA API > v3.
   
   Is it on the roadmap ?
   
   ### How to reproduce
   
   The error is on step 2 using only the jira connection : 
   
   <img width="1236" height="190" alt="Image" 
src="https://github.com/user-attachments/assets/af990dc7-6c00-4c23-bf62-228d44b4ba0f";
 />
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0-beta1@60faf14
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to