I've been trying to set up Portfolio and decided to start small so that I could understand how the scheduler works.
I've read all the documentation I could find (and various blog posts) but this automatic Scheduled Start/End date assigned by portfolio remains a mystery to me.
If someone could please elaborate on how this works cause I've spent several hours trying to figure out why I'm seeing something completely different than expected.
Release - I'm working with one release to make it simple. I've set the release date to be dynamically calculated based on my estimates (see screenshot - releases)
Team - also here I have created a very simple setup, one team, scrum, 1 week iteration, 120h capacity (see screenshot)
Scope - If I look at the scheduler, Portfolio has calculated that the release (or more specific, certain bugs within the release) will be finished on 08/07/20 and I have no idea why. (see screenshot)
These bugs are on a sprint that is scheduled to finish on 21/10/2019, there is more than enough capacity in my team and the estimates are really small (0.5h), I would have expected that this entire release will be finished by the end of the sprint on 21/10/2019 and yet, for some unknown reason the release is planned for 08/07/2020 which is more than 10 months from now whilst the combined estimated time for all the issues in this release is not more than 6 hours.
Why does portfolio calculate that the release will be 10 months from today for 6 hours of estimated work?
Please help cause I've lost so much time and patience trying to figure the logic of scheduled end dates on stories :).
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