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

The GreenHopper Issue Burndown Chart works on the same principles as the hour burndown, but is based on the complete and incomplete issues. Used together with your context, you will have a powerful tool to help you see and analyse fluctuations in the issues for your version.

To view the issue 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 'ISSUE BURNDOWN CHART' from the dropdown next to it. The issue 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, by clicking the 'Views' menu and clicking 'Printable'.
  5. The issue burndown chart* provides you with the following information:
    • Burndown chart — The number of incomplete issues remaining until the version release date.
      (info) 'Incomplete issues' are issues which have not entered the final stage (on the right-hand side) of the Task Board.
    • Burndown chart - Ongoing (dotted line) — The number of remaining issues completed 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 issues to be completed until the version release date, based on the actual issue completion data from the start of the project.
    • Guideline — The ideal burndown. This is computed with the remaining estimates, not the original estimates of the issues at the version's start date. Hence, this calculation makes the guideline slope more accurate and precise.
    • New issues — The number of new issues created.
    • Required daily burndown rate — The daily rate of issue completion required to attain your goal.
    • Required daily burndown rate - Ongoing (dotted line) — The daily rate of issue completion 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.

Screenshot: Issue Burndown Chart