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
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 .
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 ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I changed the rule to {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}
But it shows only that config change for 2 hours and nothing changed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you show me a screen capture of your automation ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Before this rule, there was {{#=}}{{issue.subtasks.original estimate.sum}}
Which caused that problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Erik Avetisyan
Not yet but i will show me what unit time using your jira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.