In the New Jira Issue View, when creating an inline subtask which has a field required, Jira won't remember the subtask type

Summary

In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the screen used by the "create issue" operation, a screen will pop up so that the user fills the data for the required field.

In this moment, Jira won't remember which subtask issue type the user has previously selected. You can view the following video about this:

JRACLOUD-71782.mp4

Steps to Reproduce

• Access an issue (that is not a subtask) using the New Jira Issue View;
• Be sure you have multiple subtask issue types available;
• Be sure you select a subtask issue type which has a required field in the screen used by the "create issue" operations;
• Try to create a new subtask;
• Select a random subtask issue type;
• Fill the Summary field;

Expected Results

• Jira will open a popup, and the random subtask issue type selected.

Actual Results

• Jira will open a popup with the first subtask issue type available

Workaround(s)

• Although probably not feasible, a workaround would be admins to make the field in the screen used by the "create issue" operation optional.