narrowizard opened a new issue, #8319: URL: https://github.com/apache/incubator-devlake/issues/8319
### 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 In the Jira plugin, the issue_convertor logic sets the issue type of subtasks to SUBTASK by default. https://github.com/apache/incubator-devlake/blob/e0584d67f543ec4e736950e51792922779e4d759/backend/plugins/jira/tasks/issue_convertor.go#L138-L140 However, if an issue type mapping rule is configured, the mapped issue type is still overwritten by SUBTASK, which does not match the expected behavior. ### What do you expect to happen When an issue type mapping rule is configured, the mapped issue type should be retained and not be overwritten by SUBTASK. The issue type for subtasks should only be set to SUBTASK when no mapping rule is specified. ### How to reproduce 1. Configure Apache DevLake to collect data from Jira. 2. Set up an issue type mapping rule to map a specific subtask issue type to another value. 3. Run data extraction and observe the transformed data in the domain layer. 4. Notice that the issue type of subtasks is always set to SUBTASK, ignoring the mapping rule. ### Anything else _No response_ ### Version release-v1.0 ### Are you willing to submit PR? - [x] 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
