[Bug][Jira] issue_convertor Overwrites Mapped Issue Type with SUBTASK

[narrowizard]

Search before asking

• I had searched in the issues 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.

incubator-devlake/backend/plugins/jira/tasks/issue_convertor.go

Lines 138 to 140 in e0584d6

	if jiraIssue.Subtask {
	issue.Type = ticket.SUBTASK
	}

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?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct