Rule for 'update parent Original Estimate if child Estimates changed' is getting set to 0m

Dan H January 10, 2022

This was previously working using the following calculation but now it seems to have stopped working properly for some reason :(

{{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}

 


Here's the entire rule:

Original Estimate changed on sub-task → update total estimate on parent

1.jpg

For reference: the Issue Types used above are all sub-tasks.


2.jpg


The rule is actioned as a SUCCESS in the logs and so here's how it looks on the ticket's History:

3.jpg

1 answer

0 votes
Eric
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 12, 2022

Hi @Dan H 

 

When editing the original estimate field, can you please try dividing by 60 instead?

 

Seems like when we read we get the value in seconds but when setting it expects the value to be in minutes. 

 

Not sure if this is regression or what caused this. I figured this out by creating a similar rule to yours and played around.

 

Hope this helps.

 

Eric

Dan H January 24, 2022

Hey Eric,

Unfortunately changing the calculation to:

{{#=}}{{issue.subtasks.original estimate.sum}} / 60{{/}}

had the following effect,,,

weeks.pngWhich I know is incorrect as the sub-tasks are made up of only days and hours worth of work - so despite in the instances where the Rule did successfully run - the estimate totals are well off here.

:(

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events