Changing request type using automation rules causes issues to get into an invalid workflow state

Summary

When using an automation rule to change the request type for an issue if it's modified to an issue type with a different workflow and it doesn't contain the current status, the issue will remain in the same status even though this status is not present in the new workflow.

Environment

JIRA ServiceDesk

Steps to Reproduce

1. Create SD project with two requests types associated with two different issue types;
2. Associate each of the two issue types with two different workflows that don't share statuses;
3. Create an automation rule to change the request type from the two created;
4. Execute the automation rule in an issue.

Expected Results

The issue should be transitioned between workflows with no problem and the status should be updated to match with the new workflow.

Actual Results

The issue remains in the status with is not correct to the new workflow. The integrity checker gives the error below:

UNFIXABLE ERROR: The issue with key TS-10 has a status of Waiting for support which is not a valid status for the issues workflow. (JRA-8326)

Partial Workaround

Disable the automation rule and contact support to fix issues in wrong status.