Remaining time estimate showing 0 to 0 in burndown chart when task completed

[Myra]

CONTEXT:

We are using JIRA Cloud. We use story points for user story estimates. For each user story we have subtasks to which we assign a time estimate. 

I am new to JIRA, so I am understanding how it works before trying it out with the team. I have created a test backlog with a test sprint.

Note that the dates assigned for the start of the sprint is set to 26th Nov 2018, whereas I created and tested the entire thing on 11 Nov 2018. So I am using future dates.

Before starting the sprint, I already divided the user stories into tasks and assigned a time estimate to each of them. So as a result, the burndown chart shows all the values for the time estimates in the time remaining column for the starting date,i.e,26/11/18 at 10:02AM.

PROBLEM:

However the problem occurs when I add time for the work logged for a task, lets say VR-5 (in the attachment 2) to 1h. This should mean that the remaining time should fall by 1h, i,e, event details should show '1h logged, remaining time estimate changed from 1h to 0'. 

Instead it shows: '1h logged, remaining time estimate changed from 0 to 0'. Also, it just changes my remaining time estimate at sprint start to 0, which doesn't make sense since at the start of the sprint there was time remaining for a task to be completed. Check VR-5 time remaining for event type, sprint start (its 0, when it was actually 1h).

Eventually the burndown chart just shows that the amount of work remaining at the start of the sprint was less when it was not , in fact it was burned down.

Note: that the time recorded for the task is ahead of the time recorded for the sprint start. That is Time when work logged: 10:30 AM 26/11/18    Time at the sprint start: 10:02

So please let me know whether my approach to testing is wrong? Has it something to do with the future dates? Or is this how jira works?

[Dmytro]

Look for RTE change event and you will see the value was subtracted. Ctrl+F the issue you're interested in and you will see that it will be in the list couple of times with different events.