Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
If the Start date and/or Due date fields on a parent issue are empty, the roadmap infers its duration based on the dates assigned to child issues. We refer to this as a roll-up. These dates automatically update as those of the child issues change, but are overridden by any manually set dates.
If your roadmap is using these rolled-up dates, you’ll see an arrow icon when you hover on the schedule bars:
In order to roll up dates:
parent issues can’t have a start and/or end date set. Manually set start and/or due dates override any inferred values. Bear in mind that manually adjusting the length of a schedule bar via drag and drop assigns a date to your issue.
all child issues need to be scheduled with start and end dates.
Roll-up values for scrum teams
For scrum teams, child issues are scheduled according to the sprint to which they’re assigned. On your roadmap, the schedule bar for all child issues is the same size regardless of their estimated duration, aligning with the sprints at the top.
These sprint dates are used to roll up dates to parent-level issues. In the example below, the parent-level task Cheddar King infers its dates from the three child issues Fermentation, Develop flavor, and Find your inner cheese. These child issues are scheduled to last two sprints, so the parent issue is begins with the first sprint and the ends after the second.
Was this helpful?