How to make JIRA use issue type screen scheme during issue move?

Question

When an issue is moved, JIRA seems to make up a screen containing all applicable fields in the destination project and issue type. It does not use the custom "Create" or "Edit" screen from the issue type screen scheme.

For example, "Create Issue" screen has 5 fields while "Edit Issue" screen has 15 fields. This is because the issue creator is not expected to know the 10 extra fields. Yet, when issue is moved from another project, the Move Issue screen has 15 fields.

Is there a way to make sure that JIRA use / respect the issue type screen scheme during issue move? In the example, Move Issue screen can reuse the Create Issue screen.

Nic Brough -Adaptavist- · Answer

I suspect you'll find it gets closed as a duplicate of https://jira.atlassian.com/browse/JRA-10348

Danny Hendargo · Answer

Here is the jac issue on this: JRA-37965.

Nic Brough -Adaptavist- · Answer

That's not true - you don't have to move issues in a "created" state and you can easily add conditions as you go through processes.  And you really should check your data that's going to be hidden, or you end up with users saying "but I put in X and it's gone"