Sum Original Estimate on parent issue

[Nofar Ben Kereth]

Hey,

I attended the webinar on June 11th, and was very happy to hear you now have the option to sum numeric fields from subtasks to its parents. 

We are using Original Estimate field and when I tried to aggregate this value on the parent I got weird large numbers as 1 day being copied as 720 weeks to the parent. 

With Story Points it worked well (tried it so I can understand what is wrong). 

Will be happy for help, this feature is super super helpful for us. 

My rule goes like that:

When value change for Time Tracking

If issue type is subtask

For Parent

      Edit Original Estimate value (smart value: {{issue.subtasks.original estimate.sum}})

[robyn · Accepted solution]

Default time tracking is in minutes -- need to divide your count to get hours/days etc.

Check your default tracking in:

https://YOURINSTANCE. atlassian.net/secure/admin/TimeTrackingAdmin.jspa 

[robyn]

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

we are using this same format but using remaining estimate and we are finding that the remaining estimates are continually added to one another. Do we need to 0 out the story on each subtask update? 

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

[Nofar Ben Kereth]

Hey Robyn! 

Thanks for your answer. 

I tried your solution and I still getting wrong sumups. 

My default unit is Hours and when I set 1 day in the subtask, the parent gets 12weeks. 

Any ideas?

[Nofar Ben Kereth]

Ok it worked when I divided it by 3600. Thanks!!

[Michael WANG]

Hi Nofar, 

I have the same issue with yours. could you share your solution for the smart value? my default unit is minutes.

[Mahesh C Narayanan]

How can I exclude QA Sub-Tasks while rolling up the original estimates of sub-tasks to story level?

[Lee Reyes]

hi. i also attended the june 11 session.

answer mentioned above is working for subtasks.
sum of subtasks under a story is rolled up to original estimate of story.

but why does the original estimate for Epic not changed?
i changed the parameters and is expecting something like "if original estimate of an issue (that has a parent) is updated, then update the original estimate of parent (epic) to sum of original estimate of underlying issues (Bug/Task/Story)"

[Stine Søndergaard]

Hey @Lee Reyes ,

Have you found a solution for this?

Best,

Stine

[Lee Reyes]

hi @Stine, no. not yet. I havent looked at the issue again since I reported it here.

[Stine Søndergaard]

Oh, alright.

Thanks for the fast reply! (:

[Duy Tran Quang]

adding subtask "original estimate" will update the parent "original estimate" value => works fine but when deleting a subtask, the parent value is not updated. Do you have any idea? 

Thanks

[Mariana Kyrova]

Hi Duy! I guess you have already solved it in the meantime :) But maybe worth mentioning: what worked for me was adding another automation rule which starts with "When Issue Deleted" and the rest is same as the first rule. 

[Carlyle Brown]

Can you add task "original estimate" to update epic "original estimate"???

or even subtasks "original estimate" to update task "original estimate" to update epic "original estimate" ???

[Parvathy Manishanker davey]

@Nofar Ben Kereth My parent story is estimated in story points and I have sub tasks for that parent. How can we sum up sub-task estimates to roll up automatically to user story level with parent issue representing estimate as story point. Can this be done? Please help

[Daniel Loewenstein]

Came across your post while looking for a similar answer. I haven't tested things out yet but I think this thread has the answer how to get the parent to automatically update with the same of store points of child tasks: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-can-you-automatically-sum-the-story-points-of-all-subtasks/qaq-p/863364

It appears that you can specify a sum operation using JSON along the lines of:

{
     "fields": {
           "customfield_10021": {{#=}}{{subtasks.customfield_10021.join(" + ")}}{{/}}

     }
}

The trick is that you have to track down the name of the field that is used for the store point estimates in your project.

[John McKiernan]

Hey all, 

Sherry, one of the engineers, who build out this new functionality posted an article answering a few of these questions. Would be good to take a look and ask any other questions you might have there :)

https://community.atlassian.com/t5/Automation-articles/How-to-sum-up-logged-hours-using-automation-in-Jira-Cloud/ba-p/1409115

Cheers,

John