- We use Quarterly PI sprints on the EPICs as "target PI" for delivery. We use that for quarterly planning per team a few Q upfront.
- When we plan the PI, we breakdown the epics to stories and assign the stories with small sprints within the PI.
- We do not remove the quarterly sprint from the EPIC level.
If you look on the advanced roadmap timeline, the roll-up dates are not always updated per the child issues, they remain with the dates of the assigned Quarterly PI of the epic.
Sometimes it works, sometimes it doesn't. can't say for sure what is the expected behavior. (the manual states that if you assign manually dates, it won't work, but it doesn't say if "sprint" is considered manually)
- We do not assign manually start/due dates to the plan
- When we remove the "Quarterly Sprint" from the EPIC, the roll-up dates are updated as expected.
- I couldn't figure out in what cases it actually worked
In the picture below:
1st EPIC - assigned with quarterly sprint. Due date is set to 31/Dec. (disregard the warnings, even when fixed, it has no impact)
2nd EPIC - without quarterly sprint - Due date is based on roll-up dates.
