cancel
Showing results for
Did you mean:
See all
##### Top groups
Explore all groups

# Automation sum-up original estimate

Lior March 31, 2024

Hello everyone

I wanted to create an automation that would roll up sum of  filed original estimate field from all the subtask to story  and the problem is that it don't sum up the original estimate to me properly

for example
i enter 1m to original estimate in subtask

This is the set automation i used  but i tried also

``{{issue.subtasks.Original Estimate.sum}}``
``{{#=}}{{issue.subtasks.remaining estimate.sum}} / 60{{/}}``
``{{#=}}{{issue.subtasks.remaining estimate.sum}} / 3600{{/}}``

Can you see in red  the result  the original estimate in story is to 1h
and if i try 2m  in subtask is change the ordinal estimate in story to 2w
there is no mathematical logic in numbers either

Thanks

#### 2 accepted

Stephen Wright _Elabor8_
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2024

Hi @Lior

I found this rule works...

• Trigger: Field value changed
• Fields to monitor = Time tracking
• Condition: Issue fields condition
• Field = Issue Type
• Condition = equals
• Branch: Related issues
• Type = Parent
• Branch-Action: Edit Issue
• Field = Original Estimate
• Value = {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}
• Field = Remaining Estimate
• Value = {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}

---

A few notes...

• I've used "/3600" as my default time unit is hours. The Original Estimate in a smart value is shown in seconds, so you need to divide it into your default unit.
• If your default unit is minutes, you would use "/60" instead
• I found setting just Original Estimate set Remaining without the time calculation - so setting both seems to work more efficiently

---

Let us know if this works!

Ste

Lior March 31, 2024

the function work , but the amount in original estimate on story it's not correct

i wrote in sub task 1h and in story i get 2w
and this is the automation rolls

Stephen Wright _Elabor8_
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2024

Hi @Lior

Was Original Estimate NULL at the time at parent-level?

If yes, are their estimate values in any of the other Sub-tasks?

---

Also, what's your default time unit?

To check this you'll need to be a Jira Product Admin, and then...

1. Go to Settings (cog icon in top-right) > Issues
2. Select Time tracking from the left-hand menu
3. Confirm what value is next to "Default unit for time tracking"

Ste

Lior March 31, 2024

Some of them yes, some of them I edited and no all the estimate it's back to wrong amount

Stephen Wright _Elabor8_
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2024

Hi @Lior

Perhaps test it on a clean set of data - i.e no estimates populated at all, and see if it still defaults to 2w?

And ensure...

• You're setting both the Original and Remaining Estimate in the rule's Action
• You've deselected the Include subtasks checkbox in "Time tracking" on the parent, as the rule is now adding this value instead

Ste

Stephen Wright _Elabor8_
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2024

Awesome, glad it now works :) - there must have been some data in the original test issues causing the 2w value.

If this answer helped to solve your query, could you accept it? That helps others who find this question in future know it could help them too :)

Ste

1 vote
YY哥
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 31, 2024

Hi @Lior

Welcome to our Community.

to edit the Original Estimate field value.

Hope it helps.
Thanks,

YY哥

Lior March 31, 2024

but it's seems like the same problem ( i tried with 60 & 3600)

I put 1H  in original  estimate on sub-task

and the automation did in original estimate in story  sum amount by 2W

Lior March 31, 2024

i don't know what is different but now is work!!!

Stephen Wright _Elabor8_ likes this
Lior March 31, 2024