In Portfolio, we've created a three tier hierarchy: Epic -> Feature -> Story. For some of our Features & Epics, the Scheduled Start & Scheduled End dates are being accurately calculated based on the sprints that the stories are in (example1 screenshot).
Other Features & Epics seem to be calculating their Scheduled Start dates incorrectly. The stories have accurate Scheduled Start dates, but the Feature & Epic do not (example2 screenshot).
This matters because Epics with incorrect Scheduled Start dates make the Schedule view inaccurately look like we're working on those Epics when we're really not.
Does anyone know why this might be and how I can correct it?
I understand why this calculation result is misleading. Something seems to be pushing your Feature to start earlier but I couldn't immediately think of a likely scenario where this would happen.
To help me understand a bit better what could be happening, could you share, out of those issues (Stories, Features and Epic), which are manually assigned to releases (and with fixed or not start/end dates), which have estimations and finally which have sprint assignment.
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