Note that this page only applies if you are using the
Classic Boards (which are no longer being actively developed;
read more).
From the GreenHopper Classic Chart Board you can display the Burndown Chart for a Custom Statistic Field (number field). Learn more about these charts here.
To view the burndown chart by custom field,
- Log into JIRA.
Select Agile > Classic in the top navigation bar. Then select Classic Chart Board from the drop-down below the project name.
- Select your project from the project dropdown (top left of the Chart Board above the 'Chart Board' dropdown), if it is not already selected. The Chart Board will refresh with information for your project.
- Using the Chart Board Navigation Bar, select the version whose chart you wish to view in the Version dropdown, then select Statistics Burndown Chart, the custom field, and Daily/By Children from the subsequent dropdowns. The burndown chart of the custom field's number of units will be displayed (see screenshots below).
Your custom field's 'number of units' could relate to anything you have defined for that field — for example, 'story points' and the 'Daily'/'By Children' dropdown is only shown if child versions are available. - 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 enabled for GreenHopper).
- 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 (see Managing Versions); or today's date, if not defined in JIRA.
- You can toggle items in the chart on and off, by selecting or clearing their check boxes in the legend under the chart.
- You can also print the chart by clicking the version's Actions menu in the Statistics Column and selecting 'Print Chart' from its dropdown. Please refer to the Chart Board - Statistics Column section for details.
- The burndown chart provides you with the following information:
- Remaining Values - Completed (solid line) ('Daily' only) — The custom field's number of units (for example, story points) remaining until the version release date.
- Remaining Values - Ongoing (dotted line) ('Daily' only) — The number of remaining custom field units burned since midnight on the current day. The gradient of this curve may change throughout this day.
- Remaining Values - Trend (dashed line) ('Daily' only) — The projection of remaining custom field units to be burned until the version release date, based on the actual unit burn data from the start of the project.
- Guideline (solid line) ('Daily' only) — The ideal burndown. This is computed with the remaining estimates, not the original estimates of the number of custom field units at the version's start date. Hence, this calculation makes the guideline slope more accurate and precise.
- Required daily burndown rate (solid line) ('Daily' only) — The daily burn rate of custom field units required to attain your goal.
- Required daily burndown rate - Ongoing (dotted line) ('Daily' only) — The daily burn rate of custom field units required to attain your goal, since midnight on the current day. The gradient of this curve may change throughout this day.
- Parent remaining values (bars) ('By Children' only) — The number of custom field units remaining by children.
Typically, 'children' relates to a series of customised time segments with each 'child' representing a 'sub' version, such as a 'milestone', 'iteration' or 'sprint'.
Daily
A 'Custom Statistic' field 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 field value for all unresolved issues in the displayed version.
Screenshot: Burndown Chart by Custom Field Units (e.g. Story Points) - Daily
By Children
If the selected version is a Parent version version, you can see the burndown chart of this version grouped by children. For example a Release burndown by 'Sprints'.
Screenshot: Burndown Chart by Custom Field Units - By Children
18 Comments
Anonymous
this doesn't appear to be working on 4.2.1, I don't see the burndown chart option, only hour and issue
Martin Gerlach
In GH 4.2.1 one has to start with this page, once a NUMBER FIELD with NUMBER SEARCHER has been added to the custom fields and screens for the projects.
http://confluence.atlassian.com/display/GH/Viewing+and+Configuring+Statistics+via+your+Planning+Board
Once, stats are activated in the planning board, the diagrams become available in the chart boards.
The charts on number fields list an issue as burned once it it's status is closed in the task board.
TS
So if you want to create a burndown chart for the sprint and you can't close the issues until the whole issue has been completed how would this work?
Anonymous
I cant see the Daily dropdown menu. What do I have to do to be able to see this?
Nick Barnes
In the Agile-> chart board, one can choose between 'Issue burndown' or 'Hours burndown'. We use Complexity points as a custom field and I would like to show the burndown of complexity points, not hours or issues. Can this be done? if so How?
Thanks in Advance!
Nicholas Muldoon [Atlassian]
Hi Nick,
Please ensure that you have the Statistic configured for Complexity Points. If you are a Project Administrator you can enable this via the Statistic button at the top of the Version column (RHS) on the Chart Board.
You can then choose the Statistic Burndown Chart as it will be configured, and you will see the Complexity Points burndown chart.
If you have any difficulty please raise a support request.
Thanks Nick.
Regards,
Nicholas Muldoon
Anonymous
How exactly are the story points grouped in the "By Children" chart above? I can't seem to work out in my head how the grouped values match the daily values in the equivalent chart shown above.
grant luna
Currently, the Greenhopper "statistics burndown chart" by "story points" considers an issue "burned" if the issue has a status of "closed" (this is my understaning of how it works). Can this be changed to burn down story points on a different issue status? Or multiple issue status? I want to chart issue burn down when the issue status is "ready for UAT" or "closed".
Nicholas Muldoon [Atlassian]
Hi Grant,
GreenHopper considers the story burned when it reaches the right hand side column on the Task Board mapping. You can remove Closed from that column and have Ready for UAT there instead.
Thanks Grant.
Nicholas
grant luna
Thanks Nicholas. One Greenhopper improvement suggestion is to allow storypoint burndown to occur on multiple status fields. Our second to last task board column is "UAT" and our last card is "Done". Some of our technical issues skip the UAT status and go directly to done. Therefore, we want our burndown chart to apply to issues in the UAT and Done status. BTW...Jira/Greenhopper is a great product.
Kees de Koning
It seems that a statistics burndown chart only shows results for issue type story?
That is, I have points defined for multiple issue types (improvements, bugs, etc), but none of these show up in the charts.
Am I missing some bit of magic configuration, or is this behavior hardcoded?
thanks a lot, Kees
Matt Robbins
Nicholas above you stated that any issue that is in a status in the right most column is considered burned. In our Chart 'Issue Burndown Chart' it shows we have 9 issues left still unburned out of 11. We have all issues that are in one of the status' that are in our right most colum which means it should show that all issues as burned.
It looks like this chart is going off of the Resolution field instaed. Am I missing something?
Kees de Koning
Tanks for your reply, I was the one missing something though... it was user error.
I defined (very handy :-| ) contexts at the beginning of the project to view only requirements, only bugs, etc.
And then forgot my graph was still set to 'requirements'....
thanks, Kees
Jean-Philippe Beaulieu
I'd like to know how the trend is calculated? I'm using the Chart Board to show a Relase Burndown in Story Points. Also, would it be possible to set a theoric velocity to show what-if trend scenario? Would be helpful in a Sprint 0...
Thanks!
Anonymous
is there a way, to set non working days or holidays in the gadget?
it doesnt align the non working days with the days set in the agile-preferences.
Anonymous
This may be a stupid question, but how can I look back at historical burn down charts, as the version pull down always shows the most active sprint for a release. I want to be able to choose any fixVersion in my pull down.
Nicole Hushka
How can I get the same burndown chart shown in the Classic Chart Board by sprint rather than by release/version in GH 6.0.5?
Anonymous
My Statistics burndown chart for story points by chidren is cutting off. I have eight children and the chart image is clipped after the seventh bar. The chart image is not scaling, it is just clipping. Anyone have this issue??