Request type is always No match if the issue type has changed by moving the ticket
Suggested solution
Automatically update the request type corresponding to its issue type
Workaround
If the Move operation involves status changing, you can use the workaround below:
- The Request type Heartware problem is associated with the Issue type Problem.
![](https://jira.atlassian.com/secure/thumbnail/320238/_thumb_320238.png)
- Create an automation rule like the one below and include all existing request types and issue types. Whenever the status of any issue changed, if the issue type is not matching with the request type, set it accordingly.
![](https://jira.atlassian.com/secure/thumbnail/320239/_thumb_320239.png)