Description

After creating new child issues under a Jira Epic (inline creation), the Summary of the recently created child issue is pre-filled for the next child issue if there are required fields, leading to a non-optimal user experience.

Currently, when a user creates child issues under a Jira Epic, if the child issue type has mandatory fields, the creation process shifts from inline creation to a modal. This modal pre-fills the Summary field with the text entered during the inline creation attempt. As a result, the Summary of the newly created child issue persists, being suggested for the subsequent child issue. This behavior can lead to confusion and additional manual steps for users to clear or change the pre-filled information.

Here is a screen recording further detailing it

• Child Task Creation: No Required Fields vs Required Fields

Steps to Reproduce

1. Start creating a child issue under a Jira Epic inline.
2. Enter a summary for the child issue.
3. If the child issue type has required fields, the process will open a Creation Modal.
4. Complete the required fields and create the issue.
5. Attempt to create another child issue immediately after.
6. Observe that the Summary field is pre-filled with the text from the previously created child issue.
7. Expected Behavior

When creating subsequent child issues, the Summary field should be empty, allowing users to enter new information without having to manually clear the pre-filled text.

Current Behavior

The Summary field of the newly created child issue is pre-filled with the text from the previously created child issue due to the shift from inline creation to the Creation Modal.

Workaround 

Currently, users need to manually clear the Summary field before entering the new information for each child issue.