How Advanced Roadmaps rolls up dates

Even though rolled-up dates are assumed values generated by the start and end dates of child issues, they’re treated the same as manually-set dates when planning with Advanced Roadmaps. Changes to the dates of child issues are automatically reflected in the rolled-up values. However, when rolled-up dates are committed back to Jira issues, only the date that currently displays is saved as a static value. The value stored in your Jira issue will not dynamically update as your plan evolves.

When rolling-up dates:

• Advanced Roadmaps rolls up target dates by default, but you can configure your plan to use custom dates or sprint dates instead. See Configure which dates Advanced Roadmaps uses for more information.

• the parent issue can’t have an assigned start or end date or be part of a sprint

• any dates you manually add will override rolled-up values

• the groups and color settings that are currently applied to your plan are maintained

If a child issue is missing a start or end date, Advanced Roadmaps displays a partial roll-up, which you can read more about on the What are partial rollups in Advanced Roadmaps? page.