Improve support for switching issue types where the switch will also include switching field configuration scheme

I had an issue reported to me today, where a team member was not able to change the type of an issue. He was only being given a subset of the available issue type. The reason was the field configuration scheme, the issue type he wished to switch to was using a different field configuration scheme, the only issue types that were visible were those on the same field configuration scheme as the current issue type.

No indication was given as to why only a subset were visible. https://confluence.atlassian.com/jirakb/some-issue-types-are-unavailable-due-to-incompatible-field-configuration-and-or-workflow-associations-278692623.html This describes the issue in more detail.

The workaround is of course to use the move option instead, but this does not feel very intuitive.

I would suggest that:

• All available issue types are available in the drop down (either inline ajax editing or the edit dialogue)
• If switching to a type with a different field configuration scheme
  • Inform the user of any fields that will lose their values as those fields do not exist on the new scheme
  • Prompt the user to provide values for any new fields which are required by the new field configuration scheme