While viewing a Story or Epic I can hit More --> Create Sub-task which is a very convenient way of creating tickets related to the task at hand. However, in light of issues such as JSWSERVER-7992 and comments such as https://community.atlassian.com/t5/Jira-questions/Sub-Tasks-on-backlog/qaq-p/909655, subtasks are NOT ideal for planning purposes.

Indeed as they are not intended for use in such a manner, many teams - including my own - avoids the use of subtasks in favour of regular tasks and Epics. As a developer, it's difficult to ignore the convienence of the More --> Create subtask workflow in favour of this alternate workflow:

1. Locate your epic. Memorize the ticket number.
2. Create a new Task. Fill in the details. Save it.
3. Return to the Epic because I got distracted and forgot the ticket number. Commit to (highly volatile) memory once again.
4. Return to the new ticket and enter the Epic Link.

Or, this workflow:

1. Locate your epic/story
2. More --> Create subtask
3. Fill in the details. Save it.
4. More --> Convert to Issue. Follow through the dialogs and save it.
5. Repeat 3 & 4 of the other workflow.

This is a request to add another option to the More submenu: Create Task

The created task will have the Epic Link filled in automatically. That's it. Nothing more fancy than that.