Summed up original estimation of subtasks

[Viren Desai]

Can the original estimation(time) of subtasks be automatically summed and reflected in the parent User Story, Task, or Bug? Specifically for the subtasks of a user story.

[Gökçe Karaduman-The Starware]

Hi @Viren Desai ,

If you are open to using a third-party Atlassian Marketplace app, I would recommend WorklogPro, which is a time tracking application. In addition to features like timesheets, reports, and viewing worklogs in a custom way, it also has a 'Total Original Estimate' field feature. With this field, you can view the total of original estimate for all the issues recursively starting form a parent issue in your issue hierarchy.

Disclaimer: I work for the vendor who developed this application.

[Rahul_RVS]

Hi @Viren Desai 

Welcome to the community !!

If you would be interested in a mktplace add-on to sum up time tracking fields or any custom number field, try out

Issue Hierarchy 

The app allows you to create a hierarchy based on standard jira structure (Epic -> Story/Task -> Subtask) or even with your issue links. You can view %complete progress at each parent level. It roll ups the time tracking fields, story point or numeric fields at each parent level.

Disclaimer : I am part of the team which developed this app

[Fabio Racobaldo _Herzum_]

Hi @Viren Desai ,

by default a parent issue will automatically retrieve all the estimation from subtasks.

Time Tracking field contains sum of subtasks original estimation 

Fabio

[Viren Desai]

@Fabio Racobaldo _Herzum_ 

Thanks for the quick response, but I'm looking for something that automatically sums up the original estimated time of subtasks, for time tracking I already enabled this setting.

[Vishal Biyani]

@Viren Desai 

There are fields that show summed up tasks from subtasks to Standard issue type.

You can refer to the field either by using aggregatetimeoriginalestimate or Σ Original Estimate.

[Viren Desai]

Hii @Vishal Biyani

Thanks for the quick response, I'm concerned about how can we add that field to the standard issue type which automatically sums up all subtask original estimations.

[Hannes Obweger - JXL for Jira]

Hi @Viren Desai

welcome to the community!

I agree that  Σ Original Estimate should give you the value that you are looking for. You should be able to just add the field to your parent issues - I don't think that there should be any side effects.

For future reference, if you want more control over how data should be summed up, there's a number of apps available on the Atlassian Marketplace that can help with this. I'll add more information below.

Hope this helps,

Best,

Hannes

[Hannes Obweger - JXL for Jira]

... and just to expand on my previous point: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

With these, you can build a view like e.g. this in just a couple of clicks:

As you can see, the summed-up original estimates update live as you enter data.

This is really just one of a virtually endless number of possible views and reports; you can also view and group by any other issue fields, configure different sum-up styles, etc. etc.

Any questions just let me know!