Burndown chart does not add new issue count/weight on the day it was created
https://gitlab.com/gitlab-org/gitlab-ee/issues/6903
This Issue has been closed in favor ofBackground:
After checking the documentation about burndown charts I checked that the displayed example of burndown showed an increase on a specific day (as displayed below). This is interesting because we can see when the "scope" of the milestone changed with more issues/weights.
I tried to replicate this behavior on my on-premises GitLab EE but I could not replicate it.
Following is my burndown (by weight, the same occurs on the "issue" graph) before adding a new issue:
Then, I added one new issue to the same milestone (weight = 3) and the issue count and weight were incremented in the overall graph as if the issue was always there since the beginning of the milestone which is not true. The issue was added today, so I was expecting to see a little increment in the graph on today's graph point and not an overall increase on the graph line
If you compare the weight graphs, the whole Y axis shifted up and when I mouse-over the first day of the milestone it says 63 instead of 60 which actually was the issue weight in the day zero of the milestone.
What questions are you trying to answer?
All this investigation lead me to ask: how can I replicate the behavior shown on the burndown documentation? Is this a bug or, if not, could you please help me understand where can I find documentation about this?
Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?
I'm trying to check if this is a bug in the burndown or if I'm missing something
What does success look like at the end of the project?
I was expecting something like the documentation show: an increase of weight on the day the issue was created.