Portfolio Plan : Why do some Epics appears as "issues without parent Epic" ??

[Myriam Goude]

Hello Dear community !

I'm struggling with Portfolio plan ..... 

We use 6 projects on Jira. Each of them a next-gen project and exactly the same config.

We defined Epics that have inside one to n stories.

Now, we want to import the Epics in Portfolio Plan. When we try to import them, only 3 of them are considered as Epics as the other Epics are displaid in the mess of Stories that are classified under " issues without parent Epics".

Why don't these Epics bring up on top when we import them ? 

[Greg Gosdeck]

i was able to remediate this my particular issue by setting the filter to:

FROM: Epic, TO:Epic

the issue was that it was trying to leverage Initiatives which is unfortunately something we do not take advantage of, meaning:

Initiative                                 <---- (PARENT)
       |_____Epic                           <---- (Child)
                  |___Story 
                            |____Task

[Henry Chad Apale]

^This is the answer right here! Make sure to utilize the Filter dropdown and adjust the hierarchy structure of your plan :) 

[philas]

Hi, i have the same problem. Any progress?

[Calum Hervieu]

I am also having the same issue. We do not use initiatives. I want to see Epics & stories, so I cannot filter from "epic to epic". Some Epics show up correctly (as the highest level in the hierarchy) in our roadmap, but others show up under "issues without parent" which are default to be hidden. Is there any solution available?

[A Li]

Wow. 4 years on still same problem since discovery :(

[Cem Kocainan]

If parent tasks are Done/Resolved, they disappear from my plan, and the child issues show as issues with no parent. 

[Greg Gosdeck]

i just tripped across this today after using Adv Road Maps for several weeks with no issues.  what is the root cause of this? 

[Deleted user]

So many years on, and I'm having the same problem. Outrageously frustrating!!!

[Nathan Funk]

I have the same problem. Does Portfolio expect that all Epics must be under Initiatives?

At the same time I'm accepting that perhaps this isn't really a problem, just that for consistency Epics that aren't under an Initiative maybe need to be grouped under something so they decided to created this as the parent item to group these Epics under.

[Cynthia Schwarz]

I am also coming across this issue. Is it something to do with the Next Gen projects?