nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Original Estimate on parent issue

Baylor Peak

Hello all,

Is there a function or feature that will automatically sum up the Original Estimate fields for sub tasks into the Original Estimate field in the parent task?

For instance, I have 5 sub tasks underneath a task that I have assigned 1 hour to each sub task. My parent task is just a container and I just want all the times of the sub tasks to populate the Original Estimate on the parent task.

Accepted answers

Mykenna Cepek

Automation in Jira (Cloud) recently added some subtask-spanning math functions that solve these sorts of problems:

All comments

Mykenna Cepek

Automation in Jira (Cloud) recently added some subtask-spanning math functions that solve these sorts of problems:

Baylor Peak

But we are not logging time. we are just entering in Original Estimate.

Mykenna Cepek

Bullet 2 in the first link talks about "Sum up remaining estimates or original estimates in all subtasks and set it to the parent task." Sounds like that's what you want to do.

The second link illustrates how to aggregate subtask data into a parent Story (using Story points, but it's the same process).

What you want to do is create a Jira Automation rule which:

Triggers on a change to the "Original estimate" field
Uses a conditional to only proceed if the triggered issue is a Subtask
Branch to the "Parent" (Story)
Set the Story "Original Estimate" field to the SmartValue {{issue.subtasks.Original Estimate.sum}}

Thus, when any Subtask is edited to change an Original Estimate, the parent Story will get updated to reflect the new total.

Baylor Peak

Yes, that is what I was working towards, but "Original Estimate" field is not available in the dropdown for Field value changed

Edmiel Leandro

Thanks for this explaining @Mykenna Cepek 🤝

Matheus Thomé

I spent many hours searching for this. It worked perfectly here. Thanks a lot @Mykenna Cepek You're phenomenal.

Monica Brazelton

I'll add to the chorus of grateful people and say thank you @Mykenna Cepek!

I was having trouble with this exact use case and it turns out my automation wasn't working because I had

{{issue.subtask.Original Estimate.sum.divide(60)}}m instead of

{{issue.subtasks.Original Estimate.sum.divide(60)}}m

Such a small difference but without the 's' on the subtasks, the rule wouldn't run properly!

Very much appreciate you posting the successful rule.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation

atl-bobross