Rollup dates on epic not expanding to include future dated sprints on Jira Plans

[Navil Narayan]

As per screenshot.

I have child items allocated to future sprints. I expect the epic to reflect that in its rolled up date, but it doesn't:

It appears to work as expected when looking at the timeline on the board itself.

Also, any idea why I can't select and change sprints in the timeline view (drag and drop) from Plans, like I can from the board timeline? This feels like a backward step to me.

[Marc -Devoteam- · Accepted solution]

Hi @Navil Narayan 

You are correct, this is also visible in the plan, as the dates in the Epic are set and not based on roll-up.

Epic should never be added to a sprint.

Here is a kb with options to remove historical sprint values from a work item; how-to-remove-previously-closed-sprints-from-an-issue 

[Navil Narayan]

Thank you!

[Marc -Devoteam-]

Hi @Navil Narayan 

Please accept my answer if this helped to answer your question.

[Chloe Reed]

This is expected in Jira Plans. Epic roll-up dates don’t always extend based on future sprints, even if child issues are assigned there—those dates show more reliably on the board timeline.

Drag-and-drop sprint changes aren’t supported in Plans by design; sprint assignment is meant to be done from the backlog or board, not the Plans timeline.

[Navil Narayan]

Drag and drop sprint changes on the timeline used to be supported - I was definitely using this feature back when it was still known as "Advanced Roadmaps".

It just seems strange that you can drag and drop sprints from the timeline in the board, and not the plan. Why was this removed?

[Navil Narayan]

So i think I worked it out. Looks like the epic was assigned to a sprint, that is now completed.

I can't figure out how to remove the historical (closed) sprint that it was assigned to in the past. I think that might be preventing the roll up of the child items sprint dates.

[Navil Narayan]

Went for option 2 at link: https://support.atlassian.com/jira/kb/how-to-remove-previously-closed-sprints-from-an-issue/

and used bulk update to remove the historical (closed) sprints that were assigned to the epic. This has fixed the rollup issue on the epic