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

   ### 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
   
   1. Configure GitHub connection, make the following configuration, collect 
code repository [GitHub - apache/incubator-devlake: Apache DevLake is an 
open-source dev data platform to ingest, 
ana](https://github.com/apache/incubator-devlake/)
   
2![image](https://github.com/apache/incubator-devlake/assets/142298906/262e72fc-9845-4b7b-b2b2-04914ce6ce12)
   
![image](https://github.com/apache/incubator-devlake/assets/142298906/b566b9b0-33de-48b2-9984-a1088ab708fe)
   
![image](https://github.com/apache/incubator-devlake/assets/142298906/6dea1615-d356-48a9-ae87-23a023fcc5d4)
   3. Check the issues table, using issue #990 as an example, the original_type 
is
   Type/feature-request, priority/low, will hit the first rule, expected type 
should be REQUIREMENT, now empty
   
![image](https://github.com/apache/incubator-devlake/assets/142298906/9a3b69ce-8b56-45ac-b703-c4074646c70b)
   
   
   ### What do you expect to happen
   
   For example [https://github.com/apache/incubator-devlake/issues/990 
](https://github.com/apache/incubator-devlake/issues/990) after collection, 
according to the configured scope config, the expected type value in the issues 
table is REQUIREMENT
   
   ### How to reproduce
   
   See above.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   0.21
   
   ### 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