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
I just started using Portfolio for JIRA. I created a new issue type - Initiative and mapped it to Initiative in Portfolio.
For some reason Initiatives Initiatives show up at the Epic and Store level in Portfolio. How do I fix that?
When an Initiative shows up in the incorrect level in the schedule it usually indicates that one or more of the source projects that are set as an issue source are coming from a Next-Gen project, as currently Portfolio is only compatible with the Classic project types, and the parent child issue mappings break when a next-gen project type is is used.
While you can set up a plan connected to a a next-gen project, the above mentioned hierarchy mappings will not function as well as various other configurations will not function covered in the following KB in more detail:
But Double check the projects imported by the plans issue sources and let me know if it is a next-gen or classic project type.