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

[Danny Hendargo]

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-]

No, it's prompting you for information that may be needed at the time of the move. If you force it to use a specific screen, you open yourself to the possibility that you might be hiding fields that it requires you to fill in. Or missing the warnings that your existing data will go.

[Danny Hendargo]

The destination project/issue type has "Create Issue" screen, which lists what fields are expected. In addition, the field configuration lists what fields are required during the issue creation. So, it makes sense to reuse the Create Issue screen and applicable Field Configuration for receiving the moved issue and guaranteeing that relevant data are supplied and not lost. Not what may be needed, but what are really needed.

As for the existing data on the issue being moved, the data will go anyway if the same field doesn't exist in the destination project and issue type. So, exposing all the fields from the destination project / issue type does not prevent data loss.

[Nic Brough -Adaptavist-]

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"

[Danny Hendargo]

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

[Nic Brough -Adaptavist-]

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