Burndown calc of remaining time.

[Jacqui]

I have started a sprint containing Stories with subtasks. The subtasks have original time and remaining set with total of 170hours across the entire sprint. 

The issue is that the Burndown chart only recognises the remaining time on the subtasks that have time burnt down.

The Project has been working as expected up to now. Also worth noting, these tickets were rolled over from a previous sprint which seems to have caused this issue and that the original estimates are calculated by a custom automation.

I've realised if I log any burn on the subtask the total hours to the sprint increase to the full value of that one ticket. 

[Abdallah Khaled]

Hi @Jacqui, I beleive this behavior is addressed in this bug: https://jira.atlassian.com/browse/JRACLOUD-87865, please validate if this is the same scenario you're experiencing, and I'd encourage you to add yourself as a watcher to be kept informed as to the state of the suggestion moving forward. Once the ticket is updated by our development team, you'll be notified via email.

[Jacqui]

Thanks @Abdallah Khaled
This certainly looks very similar, however the tickets I brought in were in TODO.