You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 ?
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)
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?
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.