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.
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
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