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?
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events