target ends in epics re-calculate the related epics due dated when the parent/related epic due dates

[Abbas Orand]

I would like to know how to recalculate automatically the due dates of the related epics if the due date of a parent epic changes.

[Trudy Claspill]

Hello @Abbas Orand 

Welcome to the Atlassian community.

Are you using Jira Cloud or Jira Server or Jira Data Center? If your URL is similar to the following then you are using Jira Cloud.

https://yourCompany.atlassian.net

Epics can not be child issues of other epics. How have you created a parent/child relationship between Epics?

[Abbas Orand]

Hello Trudy,

Thank you very much for you answer.

If epics cannot be in a child/parent relationship, they can be in a relation in terms of deadlines. I mean, one should finish so that the other start. If one has a delay, the next one should start with a delay. 

Is there a way to make these deadlines relationships automatic, so that one does not need to modify them manually.

Thank you very much again.

Best regads,

Abbas Orand

[Trudy Claspill]

Are you using Jira Cloud or Jira Server or Jira Data Center? If your URL is similar to the following then you are using Jira Cloud.

https://yourCompany.atlassian.net

After knowing which hosting option you are using, we then need to ask additional questions.

Using a roadmap/timeline feature would allow you to create dependencies between one epic and another. However, depending on your hosting type and the version (or subscription plan) you may or may not have access to native functionality for that.

And if you have that functionality it may or may not include the option for automatically resetting dates on dependent items, again dependent on your hosting type and version/plan.

And it it does not then, again depending on your hosting type and version/plan, you may or may not be able to use another feature called Automation Rules to automatically change the dates on dependent items.

[Abbas Orand]

Thank you very much for your response.

The version of the Jira that we work with is:

• v8.20.12#820012-sha1:714e321:jira-cluster-node2

I hope that this can help you to figure out the response to my question.

Best regards,

Abbas Orand