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

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Use case
   
   1. After the configuration of DevLake connections and data scopes, some 
users deleted part of Bamboo plans, some changed several Azure repos' names. 
These operations both led to a failure when re-collecting data.
   
![img_v3_028m_45afaeee-c36a-4bfa-b7c4-576e7b0060cg](https://github.com/apache/incubator-devlake/assets/14050754/0c23271b-f8b2-414a-a2c7-5aa89a4952a6)
   
   2. When users' token expire and a pipeline is automatically triggered to 
sync up data, the bp status will throw an error, but the error message is not 
that user-friendly.
   
![image](https://github.com/apache/incubator-devlake/assets/14050754/84c49a99-8652-4cd8-a0a7-ce1d4698b213)
   
   
   ### Description
   
   It's more user-friendly to add some error handlings every time before 
running a pipeline to sync up data:
   1. Test all of the connections to see if they can be successful. When there 
is a failed connection, DevLake should prompt users about the failure and guide 
users to update the token.
   2. Test if all configured data scopes can be found. When there is a data 
scope that cannot be found, DevLake should prompt users about this and guide 
users to update or remove the configured data scope.
   
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a 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: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to