YouTrack Standalone 2017.4 Help

Burndown

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.

Period-based Burndown

You can calculate the burndown based on the values that are stored in a field that stores a period type. The most common option is to track the value that is stored in the Estimation field, then burn down each issue based on the amount of time that is added to work items using the Time Tracking feature.

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 subtasks. 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.

You can also use this type of burndown without the Time Tracking feature if you set the value that is stored as spent time manually.

To learn how the values are calculated for this type of burndown, see Period Fields.

Integer-based Burndown

You can also calculate the burndown based on the values for a custom field that stores an integer. The most common usage is to use the estimations that are stored as Story Points or Ideal Days.

If follow a Scrum methodology and want to use story points for the estimation, configure and use YouTrack according to these 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.

There are two methods that you can use to measure your progress with this approach.

  • You can record incremental 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. The disadvantage of this method is that your original estimation is only visible in the issue history.
  • You can leave the original estimation untouched and burn all of the story points automatically when an issue is resolved. As you finish each user story, the amount of remaining effort is reduced. You aren't able to track incremental progress, but you don't have to update the estimation field manually.

You can use a similar approach to track progress on a per-issue basis by setting the estimation field to use Ideal Days.

To learn how the values are calculated for this type of burndown, see Integer Fields.

Issue-based Burndown

If you don't use time tracking or estimations in your project, you can still use the burndown chart. The calculation is similar to the representation for an integer-based burndown. Each time you resolve an issue, the amount of remaining effort is reduced by one.

To learn how the values are calculated for this type of burndown, see Issues Count.

Settings

Use the following settings to configure this report.

SettingDescription
Report NameThe name of the report.
ProjectsThe projects for which the report is calculated. The projects that are visible in the list are displayed based on your View Project access permissions.
QueryThe Query and Projects settings let you narrow the scope of your report to receive more precise results. The search query field supports the same syntax and auto-completion that are available in the search box.
PeriodThe time frame for which issues are displayed on the report.
Automatically RecalculateConfigures periodic recalculation for your report.
  • If you select Never, then the option is switched off. You can only refresh the report manually.
  • If you select any of the other options, YouTrack checks if the selected time period has elapsed when you open the report. If yes, the report is recalculated automatically. Reports with auto-recalculation enabled can still be recalculated manually.
Estimation FieldThe report can use the number of issues in the selected project or an estimation field. To calculate the estimations properly, all of the selected projects should store estimation values as the same data type. When time tracking is enabled for all of the selected projects, you can select an estimation field that stores a period type.
Visible toSets the visibility for the report. By default, the report is visible to its owner only.

Example

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.

SettingValue
ProjectsAdministration
PeriodMay 1 - 31, 2014
Estimation fieldIssue Count

burndownNoIdealWithPopup

Calculations

The values that are displayed on the line graph are based on the data type of the value that is used for estimations.

Period Fields

If the report uses a period-type field for estimations, the values on the report are calculated as follows:

ValueDescription
Ideal BurndownThe first value at the beginning of the timeline is the the total estimation value for the selected period. The line is drawn to the end of the timeline where the unfinished estimation is zero. Each point along the graph represents the amount of estimated time that is expected to be unspent 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 EffortShows the actual unspent estimation in the issues that remain in an unresolved state for each day. This value is reduced by the total estimation for each issue that moves to a resolved state on that day.
Ahead of/Behind ScheduleDisplays 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.
Spent TimeShows the cumulative amount of time spent for each day. This line is only visible when the amount of time spent working on each issue is recorded in work items.

The burndown chart only calculates spent time that is added as work items to the issues that are shown on the report. Parent issues with spent time that is calculated based on the total amount of spent time added to their subtasks do not show spent time on the burndown. If you want to show spent time on a burndown chart for parent tasks, you need to add your work items to these issues instead of using time tracking for subtasks.

You can add work items to both parent tasks and subtasks, but the spent time calculation for parent tasks is inflated.

Overdue EffortDisplays the amount of remaining effort at the end of the sprint.

Integer Fields

If the report uses a field that stores estimations as an integer, the values on the report are calculated as follows:

ValueDescription
Ideal BurndownThe first value at the beginning of the timeline is the the total number of estimation values for the selected period. The line is drawn to the end of the timeline where the unfinished estimation 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 EffortShows the actual estimation value for unresolved issues for each day.
Ahead of/Behind ScheduleDisplays 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 EffortDisplays the amount of remaining effort at the end of the selected period.

Issues Count

If the report uses the issues count as the estimation field, the values on the report are calculated as follows:

ValueDescription
Ideal BurndownThe first value at the beginning of the timeline is the the total number of issues that are unresolved at the beginning of the selected period. The line is drawn to the end of the timeline where the number of unresolved issues 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 EffortShows the actual number of unresolved issues for each day.
Ahead of/Behind ScheduleDisplays 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 EffortDisplays the amount of remaining effort at the end of the sprint.
Last modified: 5 January 2018