Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,456,475
Community Members
 
Community Events
176
Community Groups

"There are no issues for the selected hierarchy" - Program view

I have created a few Plans and Programs in Portfolio over the last week and all seemed to be working fine.  Today I created a new Program and linked it to two existing Plans.  When I go to the Scope view of the Program, I see all the epics that I've pulled into the Plans.  However when I click on Schedule - it shows the two Plans with the following message "There are no issues scheduled for the selected hierarchy.  The hierarchy that I chose was Epic.  

portfolio.jpg

1 answer

Figured it out.  I know there were others who had posted similar questions in the past so hopefully this will help "un stick" you if you're still having this issue.  

"For a program to display aggregated data from plans, make sure all changes are committed across both Jira and Portfolio for Jira"

I was doing some test programs/plans as we're still in the POC phase of rolling out Portfolio.  For items to show up in the schedule view, you need to assign dates to them in the Plan and also commit those changes to JIRA.  Otherwise you get the message in the graphic above.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events