This chart shows the ideal progress vs. actual progress for any set of issues over a specified time frame.
- The ideal burndown represents the effort that is required to finish the project.
- The remaining effort represents the actual amount of work that has been performed to date.
The calculation can be based on the number of issues or any other estimation value. Unlike the agile board Burndown chart, this report is not limited to a single agile board or sprint.
When the report is calculated, the following options are available:
- Move the pointer to a point on either line on the chart to see the difference between the ideal burndown and the remaining effort.
- Click a label in the legend to show or hide the corresponding progress line in the report.
If you want to calculate a burndown report that shows remaining effort and spent time, configure and use YouTrack according to the following guidelines:
- Enable and configure time tracking in each project that you want to show on the report.
- Enter values in the Estimation field for each issue.
- Use time tracking to add work items to issues.
If your issues have parent and subtask links, the spent time for a parent task is based on the total spent time for each of its substasks. To draw the report correctly, use the Query setting to filter out the subtasks and show calculations for parent tasks only, or filter out the parent tasks and calculate the report for subtasks.
If the system-wide time tracking settings for your YouTrack server are configured incorrectly, the report cannot be calculated. For example, the work days are not defined or the hours per day are set to zero. For more information, see Time Tracking.
If follow a Scrum methodology and want to use story points for the estimation, configure and use YouTrack according tot he following guidelines:
- Add an integer-type field that stores the number of story points that you assign to user stories in each project.
- Assign story points to all of the issues that represent user stories in your projects.
- Record your progress on issues by reducing the number of story points based on the amount of remaining effort. Update the values that you store in this field manually, for example, during the daily scrum with your development team.
Use the following settings to configure this report.
A report with the following settings displays the progress in the Administration team project in May 2014. The ideal burndown is not shown in this example.
|Period||May 1 - 31, 2014|
|Estimation field||Issue Count|
The values that are displayed on the line graph are based on the data type of the value that is used for estimations.
If the report uses the issues count or a field that stores estimations as an integer, the values on the report are calculated as follows:
|Ideal Burndown||The first value at the beginning of the timeline is the the total number of issues or estimation values for the selected period. The line is drawn to the end of the timeline where the number of unresolved issues or unfinished estimations is zero. Each point along the graph represents the number of issues that are expected to remain unresolved each day in order to finish all tasks by the end of the selected period. The ideal burndown is not calculated for non-working days, which are represented by flat lines.|
|Remaining Effort||Shows the actual number of unresolved issues or estimation values for unresolved issues for each day.|
|Ahead of/Behind Schedule||Displays the difference between the ideal burndown and the remaining effort. If the remaining effort is greater than the ideal burndown, the value is shown as behind schedule. If the ideal burndown is greater than the remaining effort, the value is shown as ahead of schedule.|
|Overdue Effort||Displays the amount of remaining effort at the end of the sprint.|
If the report uses a period-type field for estimations, the values on the report are calculated as follows: