I believe this might be  a duplicate of JRACLOUD-72506 – Create issue in Epic should open in a pop-up which is slightly newer but has more votes.

I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

Venkatesh, any update on this? This causes additional issues with certain add-ons that require fields to be populated on creation to work properly (but if the user doesn't want to use that add-on, the field should not be required) - i.e., Group Sign-Off.

please implement this soon

There are lot of fields are mandatory fields in our particular project's Sub-task screen. But still it is amazing to see sub-tasks issues are creating without populating the screen. That means mandatory fields also not resolved this issue

Also We have lot of other projects where sub-tasks populating the screen

Also this is not feature request so we need to vote. This purely a issue beacuse in maximum projects while creating Sub-tasks screens are populating but only in particular project sub-tasks issue created without showing the screen though the screen have multiple mandatory fileds

Please check with priority.

FYI, if you do not want to have required fields, you can also add a custom validator on the create transition of the workflow and it will pop open the screen (add something that everyone has permission to do if you want). However, as Charles described, this leads to extra clicks since you need to pick a sub-task, enter a temporary Summary, then it will open, then you might need to change some things (I did not find it clearing the picked values).

We really would just like to have more control over this experience. In most cases we do not want a pop-up, but we cannot make that happen because one of our sub-tasks in the project has a custom validator to prevent people from creating it (so then all in the sub-tasks in that project will have a pop-up regardless of whether we want it). It would be great to have the required field and custom validator only apply to that specific sub-task and not every sub-task in the project. Would also be great to be able to hide certain sub-tasks and issue types from the list on the create screens (and from the list in the sub-task/Epic issue create section).

Hi all, 

My name's Venkatesh and I'm a product manager on the Jira cloud team. I'm looking to find out a bit more about people's use-cases regarding entering more fields when creating subtasks in the new issue view. If you had time I'd love to chat over a 20 minute zoom call to learn more about your specific problems. 

https://calendly.com/vvasudevan/jira-subtasks-interview

Looking forward to talk to you,

Venkatesh 

We find that when creating a new subtask & choosing a Sub-task type and providing a summary works decently if there are no other mandatory fields. 
However if there ARE mandatory fields, a popup is opened, and the originally chosen Sub-task type is NOT respected and neither is Originally entered Summary.  The user must start from scratch in the popup (3 extra clicks/entries before the user can properly start the creation of a subtask)

We did workaround: Made Description as required field. Popup is opened after that.

This feature is really important to us.