There is a difference how the Burndown chart behaves in between Jira Cloud and Jira Server.

• In Jira Server, the Burndown chart displays both "Worklogged" and "RTE" at the smae time.
• In Jira Cloud, time for "Work logged" event is when you start working and for RTE its when you are logging the time

Steps to reproduce:
1. Open Scrum Board settings > Estimation
2. Track time using "Remaining Time and Estimation" (attached screenshot)
3. Add issues to a new sprint and start it.
4. Log work in the Sprint Issues.
5. The "Date Started" will change according to the time you log your work but the RTE takes the current time.

For Example,

As you can see In the below screenshot, I entered time spent as 1 Hour which makes the Date Started as 1:33 PM and my current Time is 2:33 PM

attached screenshot - Screenshot 2021-03-12 at 2.33.58 PM.png

After logging time, refer to the Burndown chart, and you notice that the "Worklog " event is tracked at 1:33 PM and the RTE is at 2:33 PM

• On the other hand, if we talk about the Jira Server, both the "Work log" and "RTE" are tracked at the same time.

attached screenshot - Screenshot 2021-03-12 at 2.39.05 PM.png

Impact

We couldn't read the burndown chart properly when we migrate to the Jira server to the Jira cloud. Our coworkers couldn't make sense of the remaining time estimate graph because of different behavior between Jira Cloud and Jira Server burndown charts.