Shouldn't burndown charts take issues' due dates into account?
Description
My milestone has defined start and end dates as my issues inside that milestone. It might be only me, but it seems that those dates should be taken into account as well while plotting the line.
My reasoning is:
Let's say I have a milestone sprint1
that is a 5 days long and inside sprint1
I have 5 issues. The first issue's deadline is in two days, the second in 4 days and the 3rd, 4th and 5th are only due to the 5th day.
Day 1 passes by, issue 1 is not closed (it's still on time - due to the 2nd day) the graph will currently display:
|_________
|
|
|
That might give the wrong impression the project is delayed, when it's not. Issue 1 is only due to the 2nd day. I'd expect that line only at the end of day 2. By day 2 I'd still expect to see:
|\
| \
| \
| \
Proposal
Allow users to define if they want to take the issues' dates into account while plotting the burndown chart. It doesn't need to be the default option, but it'd be nice to have it there.
Overview
What is it? Option to take issues' dates into account while plotting the burndown chart Why should someone use this feature? to get a proper understanding of the project's progress
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml