Sum Up Original Estimations - Jira Automation

Question

So I currently had to build a lot of workarounds to get the sum of all original estimations into the Epic. But it can lead to errors, when I clone a task and add it into another epic (it is an edge case, I know, but I still want to fix this :D ) Is there an easy way of doing this?

Something like:

"{{#=}}{{lookupIssues.original estimate.sum}} / 60{{/}}"

or

"{{#=}}{{issue.subtasks.Original Estimate.sum}} / 60{{/}}"

for Epics too?

It is working for stories with sub-tasks, but not for Epics.

Best Regards

Dennis

uttam kumar bhatta · Answer

Is it giving correct value for original estimates?

I tried to use the same logic, though the rule is triggering - it is not returning correct value. Example - In a story I have created 2 tasks, task 1 has Original estimate 2d 3h & task 2 has Original estimate 7h, so for story Original estimate should display as 3d 2h, however it is showing me a weird number like 45w or in week all the time for any hour estimation also. Can anyone point the mistakes?

Iryna P. · Answer

@dennis.weinberger could you show me your automation if possible? I'm struggling to sum up estimates from stories into epics and can't get any meaningful results(((

Mykenna Cepek · Answer

Unfortunately, I have not researched Jira apps to solve this problem.

Hopefully others who have needed to address this in their instances can suggest some apps that they have found helpful.

We're currently using Tempo Timesheets to provide a solid aggregation of logged time at various levels (including Epics, but also with Accounts and Customers which are layered onto Jira by Tempo). We don't use the "timesheets" aspect of Tempo at all, but we make heavy use of the logged time reporting features which support our critical client-billing processes. This is a paid app (not cheap), but it's solid, and the time logging features (ease of entry, visibility of logged time, different views and reports, even a Chrome plug-in) really help support our time tracking needs.