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

Story with multiple fix versions is not scheduled in portfolio when one fix Version is selected


I have stories with multiple fix versions. I have noticed that all the stories with multiple fix versions do not appear on the schedule until I select both fix versions in the portfolio plan settings. 


This is a big problem because the plan needs to go off of one single fix version, regardless of what other fix versions might be associated--not both.  


The story scheduling factors shows:

This issue is not appearing in the schedule. This may be because:

  • You need to recalculate your plan

1 answer

Hi Liz,

did you find a solution?

If not: are the target dates calculated automatically when excluding one of the fix versions (releases) in the issue sources? What happens when you type in the target dates manually?



I've tried a few times to tinker with it by issue sources, I too thought there had to be a way. Basically it was the same issue with each way I tried to include or exclude the issues. Even if I do get it working with a jql filter in between it guts my core use case for Portfolio if I can't filter smoothly between scenarios and fix versions. So I put that workaround on hold -- high effort and (for me) low value. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events