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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Initiatives show up at the Epic and Store level in Portfolio. How do I fix that?

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?

1 answer

0 votes

Hello Anjelika,

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.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events