in my Jira Next-Gen project I had a Task with three subtasks and converted the task into an epic.
My expectation was, that Jira automatically converts the three subtasks into tasks of that EPIC. However this was not the case...Those subtasks are still subtasks which are floating around without a parent and which are hard to track down, because they do not show up in the backlog, board or anywhere else.
If you do not know the ticket number to browse them directly I can not find them anymore...
Anyone else had this issue and knows a handy way around?
Ok, there's a couple of tricks here.
The sub-tasks are not true orphans. They appear to have lost the link to their parent, because the parent is an Epic, and there is even an "add parent" in the tools menu for them. They don't look like they have a parent, and the parent has disavowed them.
But the data for the link is still there in the background and you can get to them in two ways
I'm a bit surprised Atlassian did it this way. Ideally I'd like a "convert sub-tasks to stories, or tell me a new parent" question, rather than wilfully orphan them. Either one of those would be good enough for me (but I'd like both options)
Not really "advice" here, in my opinion, more an explanation of the underlying data and a criticism of what Atlassian have done!
And, of course, total agreement on "Strange". Bug - I'd say that too. The search, the data, meh, but definitely a bug if you leave sub-tasks hanging. Great that we have "add parent", but that's totally the wrong way to "fix" it. You shouldn't allow it!
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events