Hi Atlassian community,
Sherry here, one of the engineers from the Jira automation team!
Lots of people have been asking about one of our new features which allows you to:
Sum up logged hours of all issues in an Epic
Sum up remaining estimates or original estimates in all subtasks and set it to the parent task.
And lots more
You can now sum up numerical fields such as Story points and worklogs using Jira automation. If you want to learn how to do it, check out this blog. In this post, I just wanted to take the chance to answer some common questions that have popped up in recent webinars since users have started experimenting with it.
Many would think to use simply sum over log field like “Original Estimate“ (as we use it to sum up “Story points”) like below
{{issue.subtasks.Original Estimate.sum}}
But this gives outputs not as expected.
The short answer is that the default time tracking unit in Jira is minutes and this will sum up the time in SECONDS, so a smart value like below will print off a larger number than you might expect.
Sum function works for "numbers" but since time tracking is done in either minutes or hours or days, summing up tracking fields starts giving undesirable output.
First of all check the default time tracking unit in your Jira instance which would be MINUTE, by default, for most of the people
https://YOURINSTANCE. atlassian.net/secure/admin/TimeTrackingAdmin.jspa
If it is set as minute, divide the sum by 60 to get hours/days
{{#=}}{{issue.subtasks.remaining estimate.sum}} / 60{{/}}
If it is set as hour, divide the sum by 3600 to get hours/days
{{#=}}{{issue.subtasks.remaining estimate.sum}} / 3600{{/}}
Let’s take a look at a sample rule in context.
It updates ‘Original Estimate’ of parent if any child issue/task is created.
This feature can be used to track total “Remaining Estimates“ or total “logged“ work in an Epic or any Parent ticket.
If you have any questions, please feel free to comment below 🙂
Sherry Goyal
54 comments