Burndown chart not displaying ongoing and trend correctly

MatthiasG August 31, 2011

We are having a little problem with our burndown charts. Even though we have stories listed and assigned story points. The burndown chart (by story points) always displays a horizontal line on the chart for ongoing and trend.

In other installations the moment a story was moved to in progress the ongoing and trend was updated to reflect that. Meaning the thick dotted line was pointing down. Now the graph always correctly shows the number of resolved points and remaining points but in progress stories are handled as if they were not started.

This must be something simple ? Any ideas ?

7 answers

0 votes
Sunil Yadav February 12, 2019

I am also facing similar issue. Somebody please guide.

0 votes
Celine Courcy November 12, 2011

I just started using GH (yesterday!) and I'm having the same problem. Ensuring that the Sprint and Parent version numbers had start and end dates resolved the issue to a certain extent but now all I get is a dotted line, where I should get the beginning of a solid one (?).

Obviously something I'm doing wrong but would really appreciate some advice.

0 votes
Tommy Nordahl
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2011

We have the same issue. I need to understand the ongoing curve in detail. Where is it getting its data?

0 votes
Tommy Nordahl
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2011

We have the same issue, any idea?

0 votes
MatthiasG September 15, 2011

sadly we still have this issue ... anybody any idea ?

0 votes
MatthiasG August 31, 2011

I had already thought of that, sadly thats not it...

Taskboard

Chart

0 votes
Deleted user August 31, 2011

Can you check if the start date for the sprint is mentioned. I had a similar issue and the start date turned out to be the culprit.

Suggest an answer

Log in or Sign up to answer