Forums

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

Automation sum-up original estimate

Erik Avetisyan May 30, 2024

I created a rule that had to sum up the estimation of subtasks. hours in the User story original estimate. But It shows the wrong result.
For example, I have 9 subtasks which hours summary is 23 hours
but the original estimate gets 3w 2 hours

1 answer

0 votes
Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 31, 2024

Hello @Erik Avetisyan 

In the absence of screenshots, I think the error comes from the time unit in your smart value.

If you're retrieving a total value in seconds, it might skew the data.
I recommend adding a log to check the result.

In my case, I have to adapt because smartvalue show in seconds unit . 

2024-05-31 10_34_36-Window.png

 

 

Erik Avetisyan May 31, 2024

I have no error in the logs
However, your screenshot has a different value. My rule does not have any numbers.
Should I change my rule ?

Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 31, 2024

Hello @Erik Avetisyan 

When i mean error is error from unit time and not error from automation, that why i suggestion you to add a action "log action" with your smart value 2024-05-31 11_07_23-Window.png

In my automation, all sum orginal subtask = 12hours 

I am using audit logs to determine the sum of all original estimates sutask .

When I see that the estimates are calculated in seconds, I can't to use this value directly, iT will add 43,200 hours to my parent issue field . Maybe it the same case for you

That’s why I am using a mathematical calculation to divide by 3,600 to convert the value to hours. 

 

Erik Avetisyan May 31, 2024

I changed the rule to {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}
But it shows only that config change for 2 hours and nothing changed

Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 31, 2024

@Erik Avetisyan 

Can you show me a screen capture of your automation ?

Erik Avetisyan May 31, 2024

Screenshot at May 31 17-38-14.png

Erik Avetisyan May 31, 2024

Before this rule, there was {{#=}}{{issue.subtasks.original estimate.sum}}
Which caused that problem

Erik Avetisyan May 31, 2024

Screenshot at May 31 17-41-24.png

Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 31, 2024

@Erik Avetisyan 

Can you add a element like this capture, that allow you to check audit log on your automation the value and unit of time . As a same case my screenshot

I'm able to see 43200 is mean unit is second

2024-05-31 17_32_30-Window.png

Erik Avetisyan June 2, 2024

will it solve the problem?

 

Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 3, 2024

@Erik Avetisyan 
Not yet  but i will show me what unit time using your jira 

Suggest an answer

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

Atlassian Community Events