Using A4J to clone issues from a team-managed project into another does not automatically map issue types

Issue Summary

Automation for Jira does not automatically map issue types when cloning issues among Team-managed projects.

Steps to Reproduce

1. Create an automation rule (can be triggered by JQL) that clones issues from one team-managed project into another
2. Run the automation.

Expected Results

Actual Results

Note that the issue is also reproducible when cloning a company-managed project onto another. The automation rule associates the issue type with a Team-Managed issue type instead

Workaround

No workaround at the moment.