Hi guys,
Anyone capable to explain how one of my EPIC ended up with Sub-tasks? And how can I replicate it - considering my current hierarchy.
I wasn't trying to, but I would appreciate to have this possibility.
This behavior was previously reported in the following bug:
Link to issue link
However, it has been marked as “Won’t Fix” by the Jira Product Manager, who provided the following clarification:
Hey all,
Thank you for sharing your feedback on this behaviour. After reviewing, we’ve determined this is not a bug, so I’m closing it as “Won’t Fix.”
While our recommended best practice is to leverage hierarchy of issues and for sub-tasks to be used as child issues below a story-level issue, this is not strictly a requirement.
Customers have long been able to create sub-tasks under different levels of hierarchy and many customers continue to need this flexibility.
We don’t intend to encourage this approach so the functionality for creating a sub-task on Epics+ is not as prevalent. But you may find areas in Jira where sub-tasks can be created or moved under Epics / higher levels to accommodate specific use cases.
We appreciate you flagging this as a possible bug. I hope this helps explain the behaviour available today.
Kind regards,
Rhys | PM, Jira Plan
Although this is not a recommended approach, the functionality exists and is available in certain scenarios. If you wish to replicate this functionality, you can convert a standard issue type (e.g., Story) to a Subtask and assign it to an Epic as its parent during the process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
sub-tasks below epics are perfectly possible in Jira - it's just that recently, this option has been hidden in the issue view UI in Jira Cloud. (I believe it is still there in Jira Data Center.)
So it could be that the sub-tasks have been created,
Hope this helps,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @heider.souza , I would call in years past coming across this in a community post. I don't recall the specifics but I want to say it was related to a move or delete operation gone bad. However there has been some time and I would be surprised if that bug still existed. I would be curious to know what the breadcrumbs shows when you click on one of those sub tasks. That is what is the parent of the subtasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! Thanks, well I was trying to do this but I just did by accident :)
The parent is the EPIC itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have been racking my brain trying to recall and search the community, but haven't turned anything up. I would open a support ticket on this and if you do, please report back here your findings. Unless this is some new feature, and I sure hope not, it must be some sort of a bug. While I would love to be able to display sub-tasks within the epic detail view, I would not want it as shown as in your image. The sub-tasks should be displayed under their associated story/task parent. Epics should not have sub-tasks directly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Perhaps it was caused by either:
- a Level 0 issue, that had subtasks, being converted to an Epic
- a Level 0 issue, that was a child of the Epic, being converted to a subtask
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Reasonable theory Trudy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.