• Products
  • Documentation
  • Resources

Jira Automation docs have moved

All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs.

Go to Cloud Automation documentation | Why did we do this?

Roll up dates on your timeline

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:

When the roadmap is rolling up dates, you'll see these arrows on your Jira Software Cloud issues

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.

What you'll see when you roll up dates in your project roadmap in Jira Software Cloud

 

Additional Help