Problem Definition

When cloning issues between two JSM projects using same Screen Scheme, Issue Type Scheme and request types, does not set the Request Type for the new (cloned) request. The default request type in the project is not used in the new request.

Steps to reproduce

• Create two JSM projects using the same screen scheme, issue type scheme and request types. Set a default request type for the project by enabling project settings --> Features --> Default request types

• Manually clone a ticket from one project to the other project. Verify that the request type is set.
• Now create an automation rule to clone a request from one project to the other.

• Execute the Automation rule and you will see that the request type is not set. 

Suggested Solution

If the default request type is set, the automation rule action Clone Issue into  should set the default request type. This would be inline with the behavior when using manual cloning of issues.

Workaround

After using Clone Issue into action, use Edit Request Type component with Most recently Created Issue branch. Set the request type for the cloned issue