Subtasks which show 0m remaining on the active sprint board even with hours remaining, is this a bug

[Brenda Strech]

On my board in the active sprint I have a few subtasks which are showing 0m even though the task has a time estimate and no time has been logged.

Is this a bug?

[Yatish Madhav]

Hi Petter and Brenda ...

I am also a little confused with the answer on this post. It would make sense for the estimate on the board / active sprint view to show the auto-calculated value of orig estimate - logged work / remaining estimate.

As example I have a ticket that had 3h estimated time and then had about 5h work logged on it ... but still had some more to do on it. It showed 0m on the board view. Then I changed the original estimate to 2d. Even then it shows as 0m.

It does seem buggy ... unless I am really not understnding this ...

Thank you in advance.

[Brenda Strech]

I responded to the first answer. It doesn't resolve my issue.

[Yatish Madhav]

Hi. Thanks for the response, Brenda ... Glad I am not the only one in this boat. I was wondering why there was no reply after the first response above. Cheers

[Petter Gonçalves]

Hello Brenda,

Thank you for raising this question.

The hours between Original Estimate that are not matching is not a bug, but a behavior that you can achieve if you perform some steps.

By default, the remaining time will have the same value as the time estimate when you configure it unless you manually set a different value for the remaining time when you create the Story or when you log work.

Let me give you an example:

- Let's suppose you created an issue and added 10h in the Original Estimate field, leaving the Remaining field blank or adding the same 10h, since you didn't log any work yet:

- Both fields will be added with the same values, and once you click to log work, the Remaining estimate field will be automatically recalculated to properly set the correct values: Original Estimate less the time logged

- However, if you manually set a different/not coherent value when creating the issue to the remaining estimate field or edit it posteriorly in the Log time screen, it will display an "Incoherent value", as you can see below:

This behavior happens to allow users to set unexpected log works that were required posteriorly and give you the flexibility to work as you want with the time tracking field in your JIRA reports.

Let me know if this information helps.

[Brenda Strech]

This answer doesn't resolve the original complaint.

I have a story which is created in Jira and at the time there is no estimate since it has not been assigned to a user. Also, it isn't desired to set the estimate here since there will be subtasks created.
Once the ticket is assigned to a sprint, then our team breaks up the story into subtasks each of which will have their own estimates. The subtasks correctly update the hours remaining based on logged work for the subtask. 
The issue is getting a total on the parent story. My expectation is that the parent story would aggregate the estimated hours, the remaining hours and the worked hours.