Automation: set Due date from Start date + Original estimation

[sacha_rouzkhosh]

Hello everybody,
I need to update the due date when the start date is updated but I can't find the right formula (smart value).
The idea is: Due date = Start date + Original estimate

{{issue.StartDate.plusBusinessDays(xxxxx)}}

Anyone know how to do it?
Thank you all

[sacha_rouzkhosh]

Hi,

Thanks a lot for your help.

I tried but unfortunately it doesn't do the job.

Do you have an idea about what's wrong?

[Bill Sheboy]

Hi @sacha_rouzkhosh 

Smart values are name, spacing, and case-sensitive.  And, the documentation does not list them all.  Please try this how-to article to learn the smart values you need for that expression: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Next, I note you want to increment by business days, and that function takes a number of days parameter.  Please check your original estimate, smart value as I believe that is in minutes, and so it will need to be divided to days before you use it.

Kind regards,
Bill

[Bill Sheboy]

Hi @sacha_rouzkhosh 

Please post images of your complete automation rule, including images of the details of each action, and of the audit log details.  Those will provide context to help identify what is happening.

Thanks!

[sacha_rouzkhosh]

Hi @Bill Sheboy,

Yes you're right.

Please find below the screenshots:

[Bill Sheboy]

The rules you are showing do not match what you originally asked: how to set the Due Date when the Start Date changes, adding on the Original Estimate. 

Instead the rule you posted seems to be updating the Start and Due Date of linked issues, when the Due Date changes, and setting the Due Date based on some other field.

Would you please clarify what problem you are trying to solve?  Knowing that will help the community offer suggestions which may help.  Thanks!

[sacha_rouzkhosh]

Hi @Bill Sheboy,
Here's more clarification.
Originally I wanted to shift a ticket in the timeline when its dependency is itself shifted (cascade effect).
For this to appear on the timeline, I noticed that we have to update the Start Date and the Due Date of the ticket that we want to shift.
I managed via the automation - the one I shared - to do it for the Start Date but the Due Date remains blank. That's why I limited my request to configuring the Due Date only.
When my "blocking" ticket shifts, the dependent ticket shifts well. But the Due Date is erased.
I hope my problem is clearer with these explanations.

Thanks

[Bill Sheboy]

This might be a date format difference for the Start Date and Due Date fields.  Perhaps try forcing the value with asDate or formatting as jiraDate, and write that value to the audit log to see if it contains the values you expect.  Once you have that correct it could be used in the edit.

[Laurie Sciutti]

Hi @sacha_rouzkhosh ~ here's something I did that's similar...