nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Plans - Rolling dates up multiple levels of issue hierarchy does not seem to be working

Peter Carbon

Hello,

I am having an issue where dates are not rolling up more than one level in JIRA plans unless the bottom most issue (in this case a JIRA story) has set Start and Due dates.

Here is what I am seeing:

Scenario 1:

- Story 1 has no set start and due dates, is a child of Epic 1, which itself is a child of Initiative 1

- Story 1 has been added to a sprint starting Jan 14 and ending Jan 28

- In the Timeline view of the JIRA space that Story 1 belongs to, I see that the dates from the sprint that Story 1 belongs do roll up to Epic 1, which is expected since the timeline is configured to Schedule by sprint dates, not start/due dates

- In the JIRA plan which includes work from the JIRA space that Story 1 belongs to, there is no rollup of dates from Story 1 to Epic 1 or to Initiative 1, which is unexpected

Scenario 2:

- Story 2 has a set start date of Jan 14 and set due date of Jan 28, is a child of Epic 2, which itself is a child of Initiative 2

- Story 2 does not belong to any sprints yet

- In the Timeline view of the JIRA space that Story 2 belongs to, the start and due dates from Story 2 do not roll up to Epic 2, which is expected since the timeline is configured to Schedule by sprint dates, not by start/due dates

- In the JIRA plan which includes work from the JIRA space that Story 2 belongs to, there is a rollup of dates from Story 2 to Epic 2 and unto Initiative 2, which is expected

---

Is there something I am missing here? Shouldn't the sprint dates rollup, just like fixed start and due dates do, from a Story to its parent Epic and then the parent Initiative in the JIRA plan like it does in the JIRA Board Timeline?

Thanks,

Peter

Accepted answers

Peter Carbon

I figured out what my problem was. In order for your Plan to properly show rolled up dates for Stories based on sprint dates, you need to include the JIRA Board where the sprints will be tracked. It isn't sufficient to include the JIRA Space that the Board belongs to.

All comments

Peter_DevSamurai

Hi @Peter Carbon ,

In Advance Roadmaps, date rollup up the hierarchy (Story > Epic > Initiative) relies primarily on explicit start/target dates on child issues, not just sprint assignments.

-> This differs from the board Timeline view, where sprints auto-influence rollup because it's sprint-scheduled by default.

In Scenario 1, plans prioritize fixed dates for forecasting, so if stories lack them (as in Scenario 1), rollup skips or shows incomplete, even if sprints are set.

-> That's why Scenario 2 works (dates present), but the 1 does not.

So it's not a bug problem, you just need to toggle the "Schedule by sprints" option (Plan > Settings > Scheduling) on. So in Scenario 1, the sprint dates should roll up to Epic/Initiative -> You can test by adding a story to a sprint.