Automatically recalculate DUE dates for SUBTASKS, when revising the DUE date for HEAD tasks

[Marissa Wetzer]

Hi, in our 'board' we create many HEAD tasks.

Each head task will get a certain label which creates a number of subtasks for different people on different dates via automatization. These dates are calculated via below sum:

" {{triggerIssue.duedate.minusBusinessDays(10)}} " for example. (Each subtask has its own sum, that might be different from this one.

Is it possible to make sure all subtask dates will be recalculated, when the due date for the HEAD task is revised?

I really hope this is possible, if not perhaps someone works in a similar way and found an easy work around?

Looking forward to your insights :)

[Bill Sheboy]

Hi @Marissa Wetzer -- Welcome to the Atlassian Community!

Yes, that is possible.

The rule could be triggered on a change to the parent issue's date, branch over each sub-task, and then update the date by the amount of change in the trigger issue's date.

Here is an article from @Trudy Claspill which describes a similar scenario:

https://community.atlassian.com/forums/Jira-articles/Updating-dependent-task-s-dates-when-predecessor-task-date/ba-p/2816977

Kind regards,
Bill

[Marissa Wetzer]

Thank you for the help, Bill. We tried to create it and we were able to make the subtasks respond to the head tasks but not in the way we wanted it. 

Do you think it's possible to have a short call with someone who would like to look with us? Looking forward to your reply.

[Bill Sheboy]

Probably not from this forum or with that type of question...

This is the Atlassian Community, a place where people with similar interests gather to learn and help one another.  I suspect it is unlikely a community member would take a phone call to solve a rule issue for another customer's company (except perhaps a vendor trying to sell something :^)  And as this is a volunteer community, people participate when they can, so you would not know when they are available.

And because your question is about using rules, not about a product defect, it is unlikely contacting Atlassian Support would help either: https://support.atlassian.com/contact/#/

Let's try this...please post the following to provide context for your scenario:

• an image of the complete rule, in one single image for continuity
• images of relevant trigger, branches, actions, and conditions
• an image of the audit log details showing the rule execution, with all of the areas at the right side expanded
• explain what is not working as you expected and why you believe that to be the case

With that information, multiple people will take a look and perhaps see the cause.  Thanks!