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
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
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.