An issue in the field of "Original estimate"

[benury]

Hi All, 

I found an issue in the Original estimate field of an issue. 

When you set an original estimate  and go to another tab  and return, the set value become zero.

Does anyone else getting this error? Or is there anyway to report this bug to get fixed.

Thanks

Regards,

Benury De Silva

Business analyst, Maytech Pvt Ltd

[Vishal Biyani]

@benury 

Can you share the screenshot for history tab? if it was saved and then removed, may be change log can give some clue

[benury]

Hi, It is not reflecting in the history. But I can share a screen record. 

Please refer to the attached video.

https://drive.google.com/file/d/1ZMwRRTYSuDTxF8CPdc4dNhZd4DLEGJ-Z/view?usp=sharing

https://drive.google.com/file/d/1ZMwRRTYSuDTxF8CPdc4dNhZd4DLEGJ-Z/view?usp=sharing 

[Deleted user]

I've seen several major issues lately with the original estimate, as well as time spent and time remaining. For example, I have a ticket that's showing time still remains when it is in fact overspent. 

Example:

[Vishal Biyani]

@[deleted] This is because you have include subtasks ticked.

If you uncheck this box, then see if time tracking still showing erroneous results.

[Deleted user]

Why would that matter? Can JIRA not add the time included in the subtasks into a parent task? If it cannot, then why even put that checkbox option there....without this ability there is no point in having this tool really. (for my purposes)

[Vishal Biyani]

JIRA rolls up the time entered at subtask level to standard issue type. That's what you see when checking the check box.

say 16 hours or effort estimate is entered at Story level

if 8 hours of effort is entered at subtask level, then without the check mark you will be 16h remaining, while with the checkbox, you will see 8 hours logged and 16 hours remaining at Story level.

[Summer Hogan]

I have experienced this many times. I find if I enter it more than once it sticks the second time, but it is not consistent and it is frustrating. Sometimes I forget to go and enter it twice and it messes up my capacity planner and I plan more work for my team than they can handle.