Burndown Chart fails to consider Seconds interval
Sougat Hajra
I'm New Here 
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Hi,
After adding 2 new stories in the upcoming Sprint, I started the Sprint immediately. All 3 events happened on 23/Oct/18 at 6.29 PM. But there is a gap of few seconds between these 3 events. Whereas when I checked the burndown, it shows that Scope changed in the Sprints and burndown line goes up from the starting point. [Screenshot attached here]
My understanding is that, burndown chart only considers time upto mins and not upto seconds level. That is why Burndown chart behaves unexpectedly. Please advise, if you could consider the Seconds duration as well to get correct burndown effect.
Regards,
Sougat
