Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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


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 ? 

8 answers

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)

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

Screen Shot 2022-03-17 at 2.16.28 PM.png

Hi, i have the same problem. Any progress?

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 03, 2023

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

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

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

0 votes
Deleted user Jun 23, 2021

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

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.

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

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events