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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
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?
Regards,
Phil
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.