Documentation for GreenHopper 4.4.x . 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' link's down-arrow in the top navigation bar and select 'Chart Board' from the resulting dropdown menu. The 'Chart Board' will be displayed.
  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).
    • The 'View Version' dropdown only includes versions which contain issues that belong to at least one unreleased Fix Version (and belong to a project that is GreenHopper-enabled).
    • The chart's 'Start Date' and 'End Date' are the Fix Version's dates defined on your Planning Board. If not defined on your Planning Board, the 'End Date' is the 'Release Date' defined in the JIRA version; or today's date, if not defined in JIRA.
    • 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 chart — The number of hours remaining until the version release date.
    • Burndown chart - Ongoing (dotted line) — The number of remaining hours burned since midnight on the current day. The gradient of this curve may change throughout this day.
    • Burndown chart - Trend (dashed line) — The projection of remaining hours to be burned until the version release date, based on the actual hourly burn data from the start of the project.
    • Guideline — The ideal burndown. This is computed with the remaining estimates, not the original estimates of the hours remaining at the version's start date. Hence, this calculation makes the guideline slope more accurate and precise.
    • Team effort — The total time worked by the team.
    • Team effort - Ongoing (dotted line) — The total time worked by the team since midnight on the current day. The gradient of this curve may change throughout this day.
    • Estimate 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.
    • Estimate accuracy - Ongoing (dotted line) — The sum of the Team Effort and the Burndown, since midnight on the current day. The gradient of this curve may change throughout this day, although if you have estimated your issues accurately, this line will follow a flat trend.
    • Required daily burndown rate — The daily hour burn rate required to attain your goal.
    • Required daily burndown rate - Ongoing (dotted line) — The daily hour burn rate required to attain your goal, since midnight on the current day. The gradient of this curve may change throughout this day.

(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

A known issue exists with the Hour Burndown chart — if a work log was updated then GreenHopper incorrectly uses the updated date of the work log in the Hour Burndown chart, instead of the initial logged date.

For example, if you have logged one hour of work on the 11th October 2009 the result will be a plot of 1h on 11/10/09 in your chart. If you then update
your work log entry in JIRA on the 12th October to change the time spent to two hours, GreenHopper will incorrectly plot the work log hours against 12th October 2009 (instead of plotting two hours against the 11th October).

Screenshot: Hour Burndown Chart