Planning Board

• Planning Modes
  1. Project Overview
  2. By Versions
  3. By Components
  4. By Assignees
• Context
• Configuration
• User Preferences
• Issue Views
  1. Summaries
  2. Detailed cards
  3. List
• Legend
• Statistics
• Issue Actions
  1. Issue Create
  2. Issue Scheduling
  3. Issue Ordering
• Card printing
• Synchronising
  

     Task Board

• Board Modes
  1. Compact
  2. Outlined
• Configuration
• User Preferences
• Transition Card
  

     Chart Board

• Hour Burndown
• Issue Burndown
• Metric Burndown
  1. Daily
  2. By Children
• Metric Burnup
  1. Daily
  2. By Children
• Value Chart
  1. Daily
  2. By Children
     

     Useful Links

• Quick Start
• Released Board
• Search Board
• Portlet
• Global Configuration
• FAQs
  

     JIRA Links

• Quick Start
• Documentation

I. Chart Board header

In this header you will find the start and end date of the burndown. The start date is by default the date of the first log but you can override it. The end date is the release date of the Version but you can override it. You will also be able to: Generate the chart data for the Hour Burndown chart Add non working days Note you can also set global non working days through the JIRA GreenHopper Configuration. Change your curve settings Hide/Show curves Hide/Show forcasts Hide/Show labels Change precision Change axis display (days or dates)

II. Hour burndown chart description

Burndown Curve of the remaining hours until the version release date Guideline Curve of 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 Curve of the total time worked by the team Estimation accuracy Curve of the difference between the original estimates and the reestimates Required Daily Burndown Rate Curve Curve giving the daily rate to achieve to attain your goal. Forecat curves Curves giving the forcasts of the curves based on the historic. Using the Master option to organize your versions will allow you to see the complete burndown of the master; all the master child version burndowns are merged in one. Very useful for an overview of a release with multiple iterations. LIMITATION OF THE BURNDOWN This is for all JIRA versions since the introduction of the edit worklog feature. Since there is no way for GreenHopper to associate the worklogs with the proper change logs of an Issue after this one was edited, the updated data will be registered when the update was performed and therefore looses the original start date of the worklog. You won't loose the data in the chart but the curve will be affected if the update was made on a different date then the start date.

Agile Tip (JIRA 3.9 and lower) Note that you don't need to enter a time spent in order to use the chart board. Reestimating the issues will show you a valid Burndown curve. The Team Effort curve will then be obsolete so you might want to remove it.

You can generate a simple csv report from the hour burndown charts. This report will provide the daily remaining hours and more useful information issue by issue. These data were used to draw the burndown chart. Here is a report sample:

III Issue Burndown Chart

Same principles as the hour burndown but based on the done and not done issues.
Coupled with your context, you will have a powerful tool to help you see and analyze your version issues fluctuation.

IV. The Burndown chart based on a custom field. (Number field)

From the chart board you can now display the Burndown chart for each statistics.
Learn more about these charts here

• Daily
  The issue metric value will be burned as soon as this issue is associated with a resolution.
  You will then be able to track the sum of this metric for all unresolved issues in the displayed version.
  

• By Children
  If the selected version is a Master version, you can see the burndown chart of this version grouped by children.
  For example a Release burndown by Sprints
  

V. The Burnup chart based on a custom field. (Number field)

From the chart board you can now display the Burnup chart for each statistics.
Learn more about these charts here

• Daily
  
  
  The issue metric value will be added to the total burned value as soon as this issue is associated with a resolution.
  You will then be able to track the sum of burned value for all issues in the displayed version.
  

• By Children
  If the selected version is a Master version, you can see the burnup chart of this version grouped by children.
  For example a Release burndup by Sprints
  

VI. The Value chart based on a custom field. (Number field)

From the chart board you can now display the Value chart for each statistics.
Learn more about these charts here

• Daily
  The issue metric value will be added to the daily total burned value as soon as this issue is associated with a resolution.
  You will then be able to track the sum of the burned value for all issues in the displayed version per day.
  

• By Children
  If the selected version is a Master version, you can see the value chart of this version grouped by children.
  For example a Release value chart by Sprints (more known as the velocity chart in the case of story points)