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; } } }

How to sum up the original estimate of all child issues to their parent issue.

Mohini Chandwani

Need to add up all child issues original estimate to parent original estimate.

I have tried many ways join, sum, divide/60 even web request to get all child issues where original estimate is not empty but it is not performing sum returning empty expression.

Can refer the below snap for more clarity.

Let me know for any workaround for this.

Thanks in advance.

Accepted answers

All comments

Bill Sheboy

Hi @Mohini Chandwani

You do not show in your rule what you are using to sum up the values, so would you please show that and show an image of your audit log from an execution that does not work as expected?

And you may want to look at these two posts, showing ways to do this for parent/children with and without sub-tasks involved:

Best regards,
Bill

Darryl Lee

Ohey there's also a template for this in the library:

https://www.atlassian.com/software/jira/automation-template-library#/rule/1371692

Bill Sheboy

Thanks, Darryl. I frequently forget that one for sub-tasks and end up "re-inventing the wheel" :^)

__Bill

Mohini Chandwani

Hello @Bill Sheboy ,

Rule is working fine, have referred the article which you have shared where I'm using advanced section for aggregation of all child's original estimate to parent.

Just wanted to know if my parent issue is not an Epic type, so in that scenario what we are suppose to use. I have tried "For Parent" as branch option but it is not considering the parent and I guess it is only for subtask issues, can refer the below snap.

Can consider child issues are of "Bug,New Feature,Improvement,Task" type and parent is also one of them, do we have any branch to get the parent issue of all those child or with smart values can we find out.

Thanks for the help!!

Bill Sheboy

One thing to note is what type of project and what type of "parent" you have.

For company-managed projects, epics use the epic link to connect to child issues (story, task, bug). For team-managed projects, epics connect by parent. The branches should work for both. For story/task/bug to sub-tasks, that uses that type of parent/child relationship.

Mohini Chandwani

I have tried the other branch Linked issues with relationship of "Parent/Child", but it is not updating the parent issue.

Let me know if I'm using incorrect way or wrong components.

Rachael Harkin

Fantastic Tutorial on youtube here for this....no faffing, straight foward and very easy to follow.

How to sum up story points from sub-tasks to parent issue using Jira automation - YouTube

Welcome!

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

Quick Links

Find more posts tagged with

atl-gruland

automation