Commit 9f599e8d authored by Victor Wu's avatar Victor Wu

Further clarify burndown chart functionality in docs.

parent e6d8c547
...@@ -67,6 +67,13 @@ only tracks when an issue was last closed (and not its full history), the chart ...@@ -67,6 +67,13 @@ only tracks when an issue was last closed (and not its full history), the chart
assumes that issue was open on days prior to that date. Reopened issues are assumes that issue was open on days prior to that date. Reopened issues are
considered as open on one day after they were closed. considered as open on one day after they were closed.
Note that with this design, if you create a new issue in the middle of the milestone period
(and assign the milestone to the issue), the burndown chart will appear as if the
issue was already open at the beginning of the milestone. A workaround is to simply
close the issue (so that a closed timestamp is stored in the system), and reopen
it to ge the desired effect, with a rise in the chart appearing on the day after.
This is what appears in the example below.
The burndown chart can also be toggled to display the cumulative open issue The burndown chart can also be toggled to display the cumulative open issue
weight for a given day. When using this feature, make sure your weights have weight for a given day. When using this feature, make sure your weights have
been properly assigned, since an open issue with no weight adds zero to the been properly assigned, since an open issue with no weight adds zero to the
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment