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 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.
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events