Creating sub-tasks directly under Epics or other issuetypes in hierarchy above Epic

[jeroen_wilmes]

This post is to ask attention for a bug that has been raised and will be triaged by Atlassian. I would like to encourage everyone to vote for this issue.

https://jira.atlassian.com/browse/JRACLOUD-91980 

At some places in Jira it is possible to make a subtask a child of an issue with issuetype Epic or any issue-type higher in the hierarchy.

From the issue template you can only create sub-tasks under a story. But unfortunately Jira allows with inline changing parents, to make a subtask a child of an Epic or even higher in the hierarchy.

This has been introduced by changing Epic-link to Parent. It is agains all instructions and basic principles of Jira.

What is the problem?

Using Timeline or Plans you loose track on these issues as they don't appear in the timeline. The subtasks show up as "parent-less" issues, but that is out of track in a plan. You will miss the issue in your plan and overlook it, leading to unwanted surprises.

It took us a while before we discovered this flaw but it had hurt us already a view times by missing out on it. 

Please vote for the bug!  

[Walter Buggenhout]

Valid point and - apart from the shout out to vote for the bug - decent best practice advice, @jeroen_wilmes.

Adding sub-tasks to issues ranked higher in the issue type hierarchy will cause complications in many places.