Required fields are not set when issue type is changed by inline edit.

Summary

Required fields are not set when Issue Type is changed by an Inline Edit.

Environment

• 5.2.11, 6.0.8, 6.1.5, 6.2.4, 7.1-OD-01

Steps to Reproduce

1. Take a standard JIRA installation and add a field, e.g. "Detection Phase", to Bug issue type. Make the field required in the field configuration.
2. Create an issue of some other type.
3. Change the type to Bug via inline edit.
4. Result: The required field has no value.

Expected Results

Required fields are propmted to be updated

Actual Results

Issue type can be changed via inline edit and required fields are not populated.
Another example: Changing an issue type to Epic via inline edit does not require an "Epic Name" to be set

Workaround

• Use the More > Move Function to change the issue type

Note

That the same issue occurs when an issue type is changed via the Edit Issue screen. For example, when an issue type is changed from Story to Epic via the Edit Issue screen, the Epic Name field is not displayed in the screen even though it is a mandatory field for Epics. As a result, the issue is converted from a Story to an Epic without having any Epic Name set.
Similar issue described in JRASERVER-36946