This parent issue ends before its child issues are scheduled to complete in Roadmap

[Jatuporn]

Hi,

 I have found a warning msg "This parent issue ends before its child issues are scheduled to complete." appear in all epic timelines in the roadmap. Not so sure how to make it gone.

Thank you.

[Trudy Claspill]

Hello @Jatuporn 

Welcome to the community.

Are you using the built in Basic Roadmaps functionality of the Jira Cloud Standard plan, or have you added a third part roadmap app?

Do these epics have child issues that Due Date values filled in? And are those child issue Due Dates later than the Due Date of the Epic?

[Jatuporn]

Hi @Trudy Claspill  Thanks a lot for very useful suggestion. Yes I guessed I have added one third part roadmap app, but just now already uninstalled the app. 

However, the warning mark still there. Not so sure how could I remove the Due Date and make the warning disappear? Thank you Trudy.

[Trudy Claspill]

Hello @Jatuporn 

You will need to edit the child issues and either delete the Due Date value or change it to be earlier than the Due Date of the parent Epic, or edit the parent Epic and change its Due Date to be later than the Due Date of any of the child issues.

[Jatuporn]

Thank you for your advise @Trudy Claspill I have tried to set the due date to be no value for all issues, but still the warnings do not disappear and display just the same. So is it Due Date field and Start Date fields to deal with?

[WajahatRahman]

Same issue here.  
The Epic has Due Date of 15/11/21 whereas the Story has Due Date of 14/11/21. 
It still shows the error.

[Ana Vizcarrondo]

Same problem here. None of the child issues have the due date set, the warning is still displayed.

[Jeremy Sherwood]

I have the same issue. Would love to know how to address this.

[Roberto Formicola]

Anyone solved this problem? Even if I set a valid due date on the task, I still have this problem that the task takes all the sprint time on the roadmap.

[Shailesh Chaskar]

Refer my 19 April reply - I was able to solve it.

[Roberto Formicola]

Thanks for your answer, unfortunate I have already linked my Epic to the Sprint and this does not solved my problem.

[Shailesh Chaskar]

Epic linked to current spring and task closed as part of previous sprint?
If yes

Then u need to hack and move closed task to current sprint to solve the issue.
You cannot amend current epic and assign to previous sprint, for previous start date.

[Arjun Hazari]

The fix for me was I just had to drag the epic start date ahead than child on the advance roadmap page.

[michael.rivero]

I have finally solved this. Delete the Start Date & End Date inside your Epic. That crazy exclamation point will be gone. Thank you. Please like my FB page: Artmiker Facebook Page 

[Eli Musoke]

Go Over to Board settings and -> ˇimeline and change to schedule child issues by dates 

[Eli Musoke]

Right click on the schedule bar and select remove either due date or start date 

[Shailesh Chaskar]

This issue occurs bcoz ur epic is not linked to sprint 1 as example

Some of the stories/task under the epic are part of sprint 1.

Solution - assign sprint 1 to epic, if sprint 1 is closed then move all done task to next sprint.

[Melissa Resutko]

For me, this issue happens when I add a ticket to a sprint and the sprint end date is after the Epic end date. I have no due dates on epics or tickets, but that sprint end date seems to be the issue.

[Trudy Claspill]

@Lars Vilhelmsen 

@Jeremy Sherwood 

@Ana Vizcarrondo 

@Jatuporn 

@WajahatRahman 

Given that this is a user community, not a support portal, there is not a standard that Atlassian personnel are monitoring all the posts to provide answers.

I recommend that you contact Atlassian Support directly by opening a support case via https://support.atlassian.com/ , and then post back here the response you get to share that info with the rest of the community.

[Lars Vilhelmsen]

Will there ever be an answer to this? I have several epics with this issue and have gone through tasks and stories in the epics - no due date conflicts, but Epics still show the error. 

Can we please have a fix for this?

[Lars Vilhelmsen]

(Posted as an Answer in the hope that it will get more notice than the several replies above who remain unanswered by Jira personnel)