Sum up Original estimation to Start date

Vitor Seabra_ve8ba8

Hey folks! I need some help here once I can't figure out how to keep on going with this issue.

I have the following fields and I just want to sum them up using an automation with Jira Smart Values:

• Original estimation
  • Native field
  • Type: Time tracking (I want to estimate as business days)
  • Ex: 2w, 3d, 4h....
• Start date
  • Custom field (but comes native)
  • Type: Date picker
  • Ex: 04/04/2023

The result must be the Due date field based on their sum:

• Due date
  • Native field
  • Type: Date picker
  • Ex: 04/18/2023

So, if I logged 3d in the Original estimation field and then the Start date is 04/06/2023, the Due date field should be automatically calculated as 04/10/2023 (once it is taking consideration business days).

 

Can anybody help me with the right Jira Smart Values expression?

 

Thank you in advance and I hope you are having an amazing day!

Trudy P Claspill

Hello @Vitor Seabra 

I haven't worked out all the details but I think the smart value you need for setting Due Date is:

{{issue.Start Date.plusBusinessDays(<number>)}}

plusBusinessDays assumes that business days are Monday through Friday.

<number> would be your Original Estimate value converted to days.

In my system Original Estimate is stored in the database in seconds, so I have to divide by 3600 to get hours. You would need to then divide by the number of working hours you allocate per day.

I know that is defined in the system Time Tracking settings, but I haven't tried to figure out if the value can be pulled directly from there into an automation.

So, let's say that my original estimate is 3 days. And I have 8 working hours per day.

- In the db that is stored as 86400 seconds

- Divide 86400 by 28000 to get 3 days

- Confirm that my estimate is >= 1 day.

-- If it is not, then Due Date = Start Date

-- If the original estimate is >= 1 day, then divide original estimate hours (24) by 8. Use the Ceil function to round that up to the nearest whole number, in case it is a fraction.

Then plug that number in to the smart value at the start of my answer.

 

Caveat:

I was testing this out using original estimate values that were not whole days expecting the Ceil function to round up. If my original estimate was 2.5 days, I expected Ceil to give me a value of 3. It didn't. Instead it gave me a value of 2. In fact using the "divide" function returned 2 rather than 2.5. I had to use the division math operator to get the result of 2.5. So, from that I'm not yet sure how to force a round up for an original estimate that includes 1..n whole days plus some fraction of another day.

Below is an automation rule I created just to run the calculations and print the output to a the rule's Audit Log.