Burndown (Remaining Time Estimate) Shows RTE Uptick, But Team Didn't Change Estimates

[Ashleigh Lodge]

We're new to Jira and Agile, so there's probably some gap in my knowledge, but I've Googled my heart out and still can't explain what we're seeing to my team.

We started our first sprint yesterday and saw a few tiny downticks on the red (RTE) line in our burndown chart as expected based on time being billed against tasks. However at some point this morning we see an uptick in the red line, and the data under the chart shows that the RTE went from 0h to 1h 30m. (Screenshots at the bottom)

My team swears they didn't modify the estimate, and looking at the time billing for the issue/task it seems to indicate that any time billed over the original estimate will count as a scope increase (ie. red line going up), which I didn't expect.

The original estimate for the issue was 15m, and then there were two time billing entries for it today, one for 30m and one for 1h 15m. That would be a total time of 1h 45m, which removing the original estimate of 15m, would leave us with the 1h 30m increase we're seeing.

Are my guesses re: time billing + RTE accurate? And if so, is this just generally expected behaviour in a sprint w/ task estimates like this? Thanks!

[Danut M _StonikByte_]

Hi @Ashleigh Lodge,

To see if the issue estimate has been modified or not, open the issue NKS-31 and look on its History tab. This tab displays all the changes made along the time. 

Also, if the Jira reports are not good enough for you, be aware that there are better alternatives to them, like for example our Great Gadgets app. See these articles: 

• https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063
• https://community.atlassian.com/t5/App-Central/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694 

Hope this helps.

Danut.