"Move Issue" feature - Select "Request Type" during move

Suggestion Summary

During "Move Issue"
If the selected destination "Project" is a JSM project
The user should be able to select "Request Type" instead of "Issue Type"
(The "Issue Type" would be inherently set based upon the "Request Type" selected, since all "Request Types" are associated with a single "Issue Type" in the project's settings.)

The first page/step of the "Move Issue" tool could be renamed "Select destination project and issue/request type" OR split into "Select destination project" and "Select new Issue Type or Request Type". 

Current Workflow and Consequences

Currently, when moving an issue to any other project, the first page of the "Move Issue" tool is "Select destination project and issue type".
Once a project is selected, a list of "Issue Types" from the selected project is populated.
There is currently no selection for "Request Type".

The ticket is moved and created in the new project, and is assigned the default "Request Type" from that project. The request form and issue view of the default request type might not be appropriate for all issues, depending on the fields and data that they initially contained.
Some filters that monitor issues based on some "Request Types" could be missing these issues that are plunked into the wrong "Request Type".
Some automation that is supposed to be triggered upon creation or modification of issues with the default "Request Type" could be triggered in error, and the automation which is supposed to be triggered upon creation or modification of issues with the intended "Request Type" could have been missed.

Workaround

So, to avoid the consequences listed above, it is up to the Jira Developer or Jira Service Agent who is moving the ticket in the first place to then:
-Move the ticket to the destination project
-Have some background insight/knowledge/memory of which "Issue Type" the appropriate "Request Type" is associated with.
-Open the newly generated ticket link once the ticket has finished being moved.
-Set the correct "Request Type" however:
-If the "Issue Type" that was selected during the move was actually not associated with the intended "Request Type" then the "Issue Type" must be changed first....

To sum up, this would be a huge quality of life improvement for those of us who frequently need to move issues between Jira Service Management projects.

Thank you!!