Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Due Date Automation for Epic's child issues

Elif Alverson
Contributor
July 11, 2023

Hello, 

I am trying to create an automation which will change the child/task issue's due dates based on Epic's due date. For example , if the Epic's due date is 20.07.2023 , the task's due date will be 18.07.2023. What would be the due date syntax including the Business Days? Thank you.

 

Screenshot 2023-07-11 at 10.04.02 AM.png

1 answer

1 accepted

1 vote
Answer accepted
Rudy Holtkamp
Community Champion
July 11, 2023

Hi @Elif Alverson ,

First of all, the logic of the rule is not correct. (or mine isn't ;-) )

Your trigger is create issue and then the condition is epic. After that you are going to look for belonging to the epic. But since you just created it, there aren't any.

So either trigger on change value of the due date in an epic, or trigger when you create an issue belonging to an epic.

 

I'm not sure what the requirement is for the due date is for the child issue (two days earlier?).

But the syntax should be something like this:

{{triggerissue.duedate.minusBusinessDays(2).toBusinessDay}}

 

The logic is:

  • From the epic issue
  • You take the due date
  • Substract two days
  • And that date should be a business day, if not it will return the next business date.

Note that you can also replace .toBusinessDay with .toBusinessDayBackwards then you get the previoius business date.

Elif Alverson
Contributor
July 11, 2023

@Rudy Holtkamp , thank you for your response. I have changed the automation as you suggested above and ran it. It does not edit the due dates of the child tasks even though the audit log says it is successful. Any idea why?

 

 

Screenshot 2023-07-11 at 10.53.12 AM.pngScreenshot 2023-07-11 at 10.57.14 AM.png

Rudy Holtkamp
Community Champion
July 11, 2023

Sorry my bad, change issue to triggerissue in:

{{triggerissue.fields.due.minusBusinessDays(2).toBusinessDay}}

Elif Alverson
Contributor
July 11, 2023

I made the changes unfortunately the automation still does not function as expected. 

 

Screenshot 2023-07-11 at 11.08.34 AM.pngScreenshot 2023-07-11 at 11.08.24 AM.png

Rudy Holtkamp
Community Champion
July 11, 2023

I found it. The field name is duedate, so change the smart value to:

{{triggerissue.duedate.minusBusinessDays(2).toBusinessDay}}

Like Elif Alverson likes this
Elif Alverson
Contributor
July 11, 2023

It works, thank you so very much!!!

Like Rudy Holtkamp likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events