Original estimate of subtask should sumup and show on respective story.

[Neeta Dubey]

The estimates put on subtask under any user story not reflecting on user story. Ideally it should collect all estimates from subtasks and show on user story.

Please advise.

[Trudy Claspill · Accepted solution]

Hello @Neeta Dubey 

Adding to what @Walter Buggenhout said, if you want the Original Estimate of the parent issue to show the sum of the Original Estimates of the subtasks, you could do that through an Automation Rule.

You can find an example of such a rule in my answer on a previous post:

https://community.atlassian.com/t5/Jira-questions/Sum-up-rough-estimation-original-estimation-and-time-tracking/qaq-p/2467807#U2468097

[Trudy Claspill]

@Neeta Dubey 

To get help with your automation rule please provide screen images that show your entire automation rule and the details of each step.

Also, what is the default unit of time that is used when you enter time with no qualifier? If you enter simply 10, does that save as 10 minutes or 10 hours or 10 days?

Estimate information is stored in the database in seconds. You have to take that into consideration when summing up the value. You also have to consider what the default time unit is for estimation entries.

If the sum of the data is 3600 second, that is equivalent to 60 minutes and 1 hour. If your default time unit is minutes then you would divide the sum by 60. If your default time unit is hours then you would divide the sum by 3600. Or you have to specify the time unit at the end of your calculation for the field.

[Neeta Dubey]

I changed the denominator from 3600 to 60 and that worked. I'm getting expected result. Thank you so much!

[Walter Buggenhout]

Hi @Neeta Dubey,

Indeed. This is a topic that comes back quite regularly and indeed, Jira does not sum up estimates from sub-tasks into its parent (user) story.

A story is considered as something you deliver as a whole entity and it is best to add your estimate (for that whole entity) to the story, not the sub-tasks. I cannot figure out from your screenshot if you are running sprints or not, but if you use sub-tasks as your main body of work (instead of stories), you will find yourself facing additional issues when you try to close a sprint and not all sub-tasks of a story are completed yet. This is another area where this design/reasoning has impact.

Hope this clarifies!

[Neeta Dubey]

Hi @Trudy Claspill ,

Thanks for the info, I created rule and it shows success as well however it is not showing correct data. Please see attached snip.

for NSIp-133 it should be 1d 2h which is now only 32m

similarly for NSI-33 it should 2 d or 1d 8 h.