Documentation for GreenHopper 4.0. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

To view the hour burndown chart for your project version,

  1. Log into JIRA.
  2. Click the 'Agile' menu in the top navigation bar and select 'Chart Board' from the dropdown that displays. The 'Chart Board' will display.
  3. Select your project from the project dropdown in the top left of the Chart Board (next to 'CHART BOARD'), if it is not already selected.
  4. Select the version that you want to view the chart for in the 'View Version' dropdown, then select 'HOUR BURNDOWN CHART' from the dropdown next to it. The hour burndown chart for the version will display (see screenshot below).
    • You can toggle the information in the chart on and off, by checking or unchecking the items in the legend under the chart.
    • You can print the data as a chart or as a CSV report, by clicking the 'Views' menu and selecting the desired output.
  5. The hour burndown chart provides you with the following information:
    • Burndown — The remaining hours until the version release date.
    • Guideline — The ideal burndown. It is computed with the remaining estimates not the original estimates of the issues at the start date of the version making the slope more accurate and precise.
    • Team effort — The total time worked by the team.
    • Estimation accuracy — The sum of the Team Effort and the Burndown. If you have estimated your issues accurately, this line will be flat. If you are underestimating your issues, this line will trend upwards. If you are overestimating your issues, this line will trend downwards.
    • Required Daily Burndown Rate Curve — The daily rate to required to attain your goal.
    • Forecast curves (dashed lines) — Forecasts of the curves based on historic information.

(tick) Tip: If you set up a version to be the master version of a number of child versions, you will be able to view the burndowns of the master and child version merged into one. This can be useful for providing a visual overview of a release with multiple iterations.

Worklog Limitation for the Burndown Chart

GreenHopper currently cannot associate worklogs with the proper change logs of an Issue after one is edited. The updated data will be registered when the update was performed, hence the original start date of the worklog will be lost. You won't lose the data in the chart but the curve will be affected if the update was made on a different date then the start date.

Screenshot: Hour Burndown Chart (click to view larger image)