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.
Hi folks,
I have a few projects in Portfolio (represented by Epics in Jira) that I've been struggilng to get auto-scheduled sequentally. Each Epic contains 1 or more releases, and I've set the priority for the releases and asked them to start relative to the previous release, but whenever I auto-schedule, Portfolio tries to fit in all the work items concurrently, so the first couple of releases are greatly inflated in duration since work from subsequent releases are fit in half way through.
The only way I've been able to resolve this is to set fixed start dates for the releases, but this benefit of me being able to auto calculate dates based on our backlog and velocity.
Are there any other options that I'm missing?