• Products
  • Documentation
  • Resources

How Advanced Roadmaps rolls up dates

This page refers to Advanced Roadmaps, which is a cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.

We have a separate section for documentation about the project timeline that’s included in all Jira Software plans. Go to the documentation for project-level roadmaps in Jira Software.


In Advanced Roadmaps, you can use the roll-up dates function to schedule and update parent issues based on the dates of its child issues. Advanced Roadmaps rolls up Target start and Target end fields by default. However, you can configure your plan to use custom dates or sprint dates instead. Learn how to configure and use custom dates in Advanced Roadmaps.

In order to use dynamic dates, a parent issue can’t have an assigned start or end date (regardless of which date field is configured in your plan), nor can it be assigned to sprint. This is because manually set dates override rolled-up values.

Rolling up dates is a calculation that only exists for planning purposes in Advanced Roadmaps. When you commit changes back to your Jira issues, rolled-up values are saved as a static number or text as if they’re manually set. This value stored in your Jira issue will not dynamically update as your plan evolves.

When a date is inferred, Advanced Roadmaps adds an arrow to the field that’s been rolled up, as well as a striped candy-cane pattern on their timeline bar, as shown below:

An example of rolled up dates in Advanced Roadmaps for Jira Software Cloud

If the bar fades out in one direction, you have a partial roll-up in your plan. Learn more about partial rollups in Advanced Roadmaps.


Additional Help