Breadcrumb

[Naz James]

This used to work before, but I am seeing issues.

Breadcrumb setup I have is Epic -Story - Task -Subtask.

I converted subtasks to task, and they no longer link to the proper story, instead it just links back to the epic.

I have gone into the story and also linked all the tasks with the story being the "is parent of" but it the tasks don't link back to the story.

My goal is to show the stories under the epic on the jira board view OR

just show the stories and all the tasks under it, but its not nesting properly

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

If you convert a sub-task to a story, then it is no longer a part of its parent story.  That's why the parent-child relationship has disappeared.

Atlassian has recently been changing the way the hierarchy is represented, moving from three different layers (Initiative -> Epic, Epic -> Issue, and Issue -> sub-task) that are all done differently and presented differently in older versions to a more simple looking "parent" field.

 I suspect it is this change that is changing what you are seeing, but it is only a visual change; your issues still can belong to issues, and your sub-tasks are still a part of their parent issue.

Linking is not a way to do parent-child relationships.  Even if you have a link that displays as "is parent of", the child issue may well not be part of the parent.  If, for example, you have two stories, one of them cannot be the parent of the other.  They exist at the same level.

I am not sure how to "fix" what you have now, beyond saying that you need to look at all the issues that are wrong and re-arranging them all into an Epic -> Story -> Sub-task structure (if you have Advanced Planning née Advanced Roadmaps née Portfolio, then you may have levels above Epic)

Once you have done that, I recommend renaming or removing the redundant "is parent of" link type.

[Nic Brough -Adaptavist-]

Oops, sorry, I forgot to mention one little thing.  Because Epics are issues in their own right (and all the objects above them are too), they can have their own sub-tasks.  This looks a bit weird - an Epic can have two types of child issue, Issues and Sub-tasks.  I try to never have sub-tasks on anything other than base-level issues as it's confusing, and not really a lot of use.