Showing sum of remaining time of all subtasks in story

[Maroun Maroun]

I have a story, with some subtasks under it. Each subtask has an estimation. I can see the total in the "Time tracking". However, the "Original estimate" is 0m, and it doesn't sum up all of the subtasks. As you can see in the image below, there's a dash "-". How can I replace the "-" with the total remaining time?  

The card layout includes the following:

[Nic Brough -Adaptavist-]

I am a bit stuck on what the problem is here.  Your first screenshot is showing the time tracking (original estimate, work logs and remaining estimate are all part of the time tracking field), and beneath it, the original estimate for the current issue of 0

The dash in the left-hand side looks like the sprint estimate, which is not necessarily the original estimate (but if it is set to be the original estimate, then the "-" makes sense as it is 0 on this issue)

[Maroun Maroun]

Thanks for your response. Let me clarify the issue.

I have a story, with 4 subtasks. I set the original estimate for each subtask (assume 2 hours for each). Shouldn't the "original estimate" of the story itself, which contains the subtasks, be the sum of all of the included subtasks (e.g. 8 hours)?

As to the "-", I'd like that value to hold the remaining estimate (original estimate minus time spent).

[Nic Brough -Adaptavist-]

No, the story has its own estimate and work logging.

If you then look at the "time tracking" stuff in your screenshots, you can see there is a tick-mark for "include subtasks", which toggles the display between "current issue" and "sum of current issue and subtasks"

In your other two screenshots, you're seeing some estimate fields prefixed with Σ - this sigma is used in its standard mathematical sense - it means "sum of", and when you look at it on a story, it means "sum of the value on this issue and all its sub-tasks".  It works for sub-tasks too, even though they don't have sub-tasks of their own (so it just works out as "the sum of the estimate on this issue").

For the - , the sprint estimate is never going to look at sub-tasks, they are an irrelevance to the sprint, they are not what the team commits to (they're parts of committment items)

Also for the purposes of sprints, you wouldn't use remaining estimate, it would be nonsense to burn down on a value that is going down.  You burn down a value that is the starting point.

[Maroun Maroun]

Thanks for the clarification Nic, appreciate it.

[Suvarna Gaikwad]

@Maroun Maroun can you please share with us screen configuration for Story issue type for this project?

This issue of not accumulating original efforts of subtasks to parent issue happened with one of our projects as well. And issue was there were two fields with name Original Estimate in our instance (1 with Σ symbol as prefix and 1 without it) and later (without symbol) was added to screen by mistake. The one with Original Estimate (with Σ symbol as prefix) worked in our case getting original estimates rolled up from subtasks. You can check if this works for you.

P.S. am referring to Screen layout and not card layout. Card layout seems fine.

[Maroun Maroun]

Hi Suvarna,

Yes, I have the following fields:

Summary

Descriptiuon

Attachment

Labels

Sprint

Epic Link

[Suvarna Gaikwad]

@Maroun Maroun Tried reproducing this. On view issue screen, it is still a problem because of new issue view of jira cloud. Details here. However I was able to see original estimates rolled up from subtasks in old jira issue view. (click 3 ellipsis on top right on view issue screen and click to see Old Issue View. P.S. This may not be available to you as Atlassian is transitioning everyone to new view)

Regarding viewing Original estimates on Board View, this is working for me by adding     Σ Original Estimate in Card Layout -> Backlog