nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moved Story to Epic and Lost Child Issues

Daniel_wrnkej

When I migrated a Story to an Epic, all of my child issues were lost. Is there a way to get those back or to roll back to another status? I'm sure there is a technical reason why all of these were dropped during the "move" but right now I need to find a way to not lose all those workstreams.

Comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

I am not sure I understand what you have done here, or perhaps what you're describing. The terminology is a bit fuzzy though, for historic reasons

Stories do not have "child issues", but they can have "sub tasks".

Epics do have "child issues", but they are structurally a different type of issue, and can also have sub-tasks (although the UI pushes you away from using them on Epics a bit).

So, when you say "all of my child issues", do you really mean the stories had sub-tasks, or something else?

Sub-tasks won't be removed by changing stories to issues, they remain as part of the issue.

Daniel_wrnkej

The story I "Moved" to be an "Epic" lost all of its subtasks when migrated. The subtasks did not automatically become Stories. Hope that's a little more clear.

Daniel_wrnkej

The subtasks are all gone. It appears they were deleted and I'm trying to revert the last change to try a different way of moving things to preserve.

Nic Brough -Adaptavist-

Sub-tasks would not become stories, they're sub-tasks of the issue, and the issue is still there, and Epics can have sub-tasks, so there's no need to do anything.

Jira doesn't delete issues during actions other than delete or bulk-delete. Moving the story to an epic doesn't delete anything.

Can you go to the standard issue view of the (now) Epic and check what sub-tasks it has? A second test would be to try to browse directly to one of the sub-tasks using its key (https://yourjira.com/browse/ABC-123 )

I think we might need some more detail on how you did the move (mostly about config rather than the actual move) if the sub-tasks really have gone.

I just tested it with a Company-managed project in a mostly off-the-shelf Jira system - create a story, added 3 sub-tasks, moved the story to an Epic, and the sub-tasks are still all there:

Page Partain_6qxps8

NEVER MIND: I was able to find my sub-tasks!

José Carlos De Oliveira Escalona

Hi Daniel, I have a similar issue and I wonder how you managed to find the sub-tasks without parent. They don't show in the backlog as they got no parent, I've done a search of sub-tasks without parent and none of them seems to work....

Screenshot 2024-04-22 at 18.08.29.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira