Burndown chart displaying incorrect number of issues and weight, also goes back in time occasionally

Burndown chart displaying incorrect number of issues and weight, also goes back in time occasionally

I have seen a variety of issues with the burndown charts in my students’ projects this year that I don’t remember seeing in the past:

One team frequently has both issues and weight missing from their burndown charts, as if some issues are completely missing from the chart.

Other teams have a “hook” in which the chart goes back in time one day at the end of the sprint, unlike a truly functional plot which would go forward in time only with only one value at each time

This is on gitlab.com. Does that mean we are using the latest version of GitLab?

We have tried adding and removing labels, looked for common trends in which PBIs might be included and which might be discarded, but we haven’t been able to find any common patterns.

The problem appears to have appeared before and was resolved around one year ago:

1 Like

I’m seeing a similar thing on self-hosted GitLab-EE 13.7. Group milestone lists 20 total issues, but only 6 in the burndown and… 7 in the burnup, and of course the “closed” count is wrong as a result as well.

If I could find out a bit more about why I’d maybe have enough to submit a bug report. Good to know I’m not the only one…

@steveusec Can we perhaps submit a bug report anyway? It seems that the bug is at least reproducible in the sense that we have projects that perpetually display it.

Apologies for taking so long to reply to this. It wasn’t quite high enough priority to grab my attention again. But it remains a bug-bear for me. Turns out there already an issue for this, created three months ago:

I’ve thrown some of my own examples in.