Stories which have epic links but are listed under issues without parent

[jenna lunardi]

I have a number of Stories which i have linked to epics, and those epics have parents. However i cannot get them to fall under the parents in the plans view?

Can anyone offer some suggestions?

[jenna lunardi · Accepted solution]

Got it!

The parents/epics were resolved while the stories were in progress!

I made everything above the story in progress and they magically moved themselves into the hierarchy

[Cherie]

I am having the same issue, but all of the parents are "in progress". Does anyone else have ideas? Like Jenna most of the stories have no issues, it is just a few rogue ones... (so hierarchy is correct).

[Pauline Coma]

Did anyone figure it out why is this happening?

I was thinking that it might be related to the initial query I was using to pull the issue into the plans, but I really don’t understand why some epics that have the same fields filled are displayed and some are not 🤷🏻‍♀️

[Tomasz Grochowski]

I had the same issue.
I followed all the recommendations listed above. None worked.

Finally, I fixed that. Here are the potential problems I identified:

go to Configure -> Issue sources -> Edit issue source: Advanced Roadmap query is based on versions and epics. What does it mean:

- option 1: when you choose releases, there are only 'unreleased' and 'released' versions available; you cannot select 'archived' releases; why does it matter? Because if your epic (or objective or initiative) in the FixedVersion field has an 'archived' version - that particular epic/objective/initiative will not be included in the query, and its lower-level backlog items will be visible as items without a parent. Just go to Issue Navigator, find all epics/objectives with assigned versions, and look for versions that have been archived. 

- option 2: verify if all epics are included in the query

go to Configure -> Issue sources -> Completed issues

- here, you can set the number of days completed issues are visible in the plan; why is this important? Because if you have an unresolved story under resolved epic AND the epic was resolved more than the number of days..... yes, the epic will be removed from the plan, and its unresolved story will be presented as a story without a parent; recommended fix: fix resolution in the hierarchy (open higher items) or remove unresolved item to another epic - just sync resolution through the whole hierarchy

I hope that will help to identify which particular case works for you

[Thomas Nis Westergaard]

Thanks, Option one worked for me :)

[Ievgen Korshunovych]

I have a similar issue. About a month ago the project I was running had a roadmap without any issues but then one day we noticed a suspicious new number of issues without parents. I've looked into those and did not see anything changed there, they all had parent links. Our roadmap is capturing hierarchy Initiative->Epic->(story, task, bug).

All of the epics are in different statuses among those without parents, only some issues of epic and story level are displayed like that, the majority are sitting fine within our hierarchy.

I've tried recreating the board, I have tried removing and adding parent links and nothing seems to help.

Does anyone else have this issue?

Thank you

[Pramodh M]

Hi @jenna lunardi 

You need to define heirarchy in Advanced roadmaps

Please find the reference here

https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps

Thanks,

Pramodh

[jenna lunardi]

Sorry @Pramodh M i should have provided more context, 

I have over 15,000 tickets happily sitting within the hierarchy i have defined. Including the parents of these stories.

But these 6 random stories just wont budge from "issues without a parent"

[Maciej Łukasz Wojszkun]

Check if Epics have not been removed from the plan: Configure -  Removed Issues

edit: ah sorry, just realized, this page is for cloud.