Unable to create sub-tasks for Epic level issue type

[Manuvimal Mohan]

I'm unable to create sub-tasks under issue types that are above Story level in Issue hierarchy. Can anyone please refer me to the documentation for this behavior 

[Trudy Claspill · Accepted solution]

Hello @Manuvimal Mohan 

In Jira Cloud an issue's parent can be only in the Issue Type Hierarchy level directly above the issue. Epics are two levels above subtasks, so Jira doesn't support creating subtasks as children of Epics.

The design of Jira would lead to creation of standard level issue types (i.e. Task, Story, Bug) as the children of Epics.

What problem are you trying to solve by creating subtasks directly under Epics?

If you feel you absolutely must create subtasks directly below Epics you can do so in the following manner:

1. Create a child issue under the Epic selecting one of the standard level issue types.

2. Open that newly created child issue and use the Convert to Subtask function to change it to a subtask.

3. When prompted to enter the parent for the subtask, enter the issue key for the Epic.

[Manuvimal Mohan]

This solution definitely works and interestingly after the first sub-task is created, you can use the + button to create additional sub-tasks. I assume this is just a bu

[Charlie Misonne]

Hi @Manuvimal Mohan 

Sub-task are not meant to be used under epics because it would skip a level in the hierarchy of: epic -> story/bug/... -> sub-task

It is technically possible though but I would not recommend it because it is just not convenient to create those sub-tasks under an epic.
It will probably work with the REST API or Automation rules.
And when a story containing sub-tasks is converted to an epic the sub-task remain.

Since Atlassian reworked the issue view it does not allow you to do it easily anymore. See https://jira.atlassian.com/browse/JRACLOUD-72060

I think you should just stick with the hierarchy. Having 2 different types of levels under an epic would make things weird.

[Manuvimal Mohan]

 This solution above works and I can create follow-up sub-tasks as well.