Why does my remaining estimate does not calculate correctly?

Question

It seems that for some issues in our environment, the remaining estimate is not calculated correctly :
Even though 4 hours of the original estimate were logged, in the Tempo area of the issue it shows a remaining of 1h45m?
There were no manual interventions on this issue.

What goes wrong?

Bert Duhamel · Answer

thank you for reflection.
I assume in our case, it would be useful to block the possibility to edit this particular field.  If I've got it right tis is included in the permission "working on an issue"?
Is there a way to have this field "read only" for people who work on an issue?

Duc Thang TRAN · Answer

@Bert Duhamel

Normally, when updates the worklog and the time spent is less than the initial estimate, the difference is added to the remaining estimate. They can minus this difference or  set it to zero (if before change , remaining is 0) to avoid add more time to the  remaining

Normally, you can view the log in the history of this change

For this ticket , If remaining estimate  is available in the edit screen, you can also delete the value directly.

Bert Duhamel · Answer

Thank you for your reply, as a matter of fact, I thought something like that might have happened, however in the history of the issue I couldn't find a manual correction of the remaining time.  Could this have been a manual adjustment of the remaining time performed by the person who made the logging?