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: