GreenHopper Burndown charts

We are having issues in the burndown chart.

Under Report

1. Time spent(green) is not showing. How to make it visible

2. Also the graphs shows flat line for log work and hours spent. ( how to adjust scale?)

DateIssueEvent TypeEvent Detail<abbr title="Increase">Inc.</abbr><abbr title="Decrease">Dec.</abbr>Sum<abbr title="Increase">Inc.</abbr><abbr title="Decrease">Dec.</abbr>Remaining09/05/2013 23:14FND-21904
FND-21967
FND-22641
FND-22801
FND-22806
Sprint start

0
-
0

FND-22822Scope changeIssue added to sprint

0
0
2w
2w

09/05/2013 23:15FND-22801Scope changeIssue removed from sprint

0
0
0
2w

FND-22641Scope changeIssue removed from sprint

0
0
0
2w

FND-21904Scope changeIssue removed from sprint

0
0
0
2w

FND-22806Scope changeIssue removed from sprint

0
0
0
2w

FND-21967Scope changeIssue removed from sprint

0
0
0
2w

09/05/2013 23:16FND-22822Work logged1d logged, Remaining Time Estimate changed from 2w to 1w 4d

1d
1d
1d
1w 4d

09/05/2013 23:21FND-22822Work logged4d logged, Remaining Time Estimate changed from 1w 4d to 1w

4d
1w
4d
1w

10/05/2013 12:21FND-22822Work logged1m logged, Remaining Time Estimate changed from 1w to 4d 7h 59m

1m
1w 1m
1m
4d 7h 59m

9 answers

1 accepted

See my sample chart below. You can attach your chart to this issue: https://jira.atlassian.com/browse/TST-50391

Sample GH Burndown

Files attached to TST-50391

Is there a way to display the story points associated with an issue? I thought the defaults was sub task. See attached record

Does the Issue Type have to be story or can we change it to a default sub task?

Attached to TST-50391 is another burndown report graph based on the configure values.
It appears when we add issues it will show on the bottom of the graph instead on top. See 3 files Multi*

Does the burndown chart work with linked issue as subtasks? Does it get the estimated time or do we have to use the STORY POINT field and generate a number?

0 vote
Timothy Chin Community Champion May 10, 2013

You need to give us a screenshot.

May 10
May 11
May 12
May 13
May 14
May 15
May 16
May 17
May 18
May 19
May 20
May 21
May 22
May 23
May 24
0
10h
20h
30h
40h
50h
60h
70h
80h
90h
Guideline
Time Spent
Remaining Values
Non-Working Days
<input id="ghx-chart-show-non-working-days" style="margin: 0px; padding: 0px;" type="checkbox" checked="checked"/> <label for="ghx-chart-show-non-working-days">Show Non-Working Days

</label>

I think I can address this even without the screenshot. The burndown chart will show the Estimation Statistic and Time-Tracking options that you have configured on your particular board under Estimation tab (go to Configure > Estimation). If you choose to Time Tracking = None, you will not see your hours burnup (the green line). If you choose Time Tracking = Remaining Estimate and Time Spent, then you will. But only assuming that you have actually been logging time.

Keep in mind that you have to be the Board Owner or a jira-administrator to edit the board configuration options.

I am the board owner and have Time Tracking = Remaining Estimate and Time Spent.

How do i upload a screen shot. Cut & paste above does not look good,

Issues can be estimated when in Plan mode to get an idea of how much work is being committed to in a sprint. Read more about estimation and tracking.

<form class="aui ghx-limited" style="margin: 16px 0px 0px; padding: 0px; color: #333333; font-family: arial, tahoma, verdana, sans-serif; font-size: 12.800000190734863px; line-height: 1.4; position: relative; max-width: 750px;">
<label style="float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right; word-wrap: break-word;">Estimation Statistic</label><select id="ghx-estimatestatistic-select" class="select" style="margin: 0px 5px 0px 0px; padding: 1px; font-size: 13px; max-width: 100%; width: 250px;"><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" selected="selected" value="field_customfield_10272">Story Points</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_timeoriginalestimate">Original Time Estimate</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10273">Business Value</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10210">CO - Impact Assessment, Estimated Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10211">CO - Impact Assessment, Schedule Days</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10111">Design Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10112">Development Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10170">Discovery Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10282">DueTime</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10153">Execute Test Plan Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10033">PM % Complete</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10281">PercentDone</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10173">Performance Tuning Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10374">Risk Consequence</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10474">Risk Detectability</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10373">Risk Probability</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10076">Task Hours</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10171">Tech Solution Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10172">Test Plan Hrs</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="field_customfield_10280">Units</option><option style="margin: 0px; padding: 0px 1em; font-size: 13px; font-family: arial, tahoma, verdana, sans-serif;" value="issueCount_">Issue Count</option></select>
Estimate issues in Plan mode by entering values for Story Points. Your velocity from sprint to sprint will be measured against these estimates.
<fieldset class="group" style="margin: 0px; padding: 0px; border: 0px; position: relative; clear: both; min-height: 1.6em;"><legend>Time Tracking</legend>
<input id="ghx-trackingstatistic-none" class="radio" style="margin-top: 0px; margin-right: 2px; margin-left: 0px; padding: 0px; border-style: none; float: none; width: 15px; height: auto; vertical-align: middle;" type="radio" name="ghx-trackingstatistic" value="none_"/><label style="float: none; display: inline; left: 0px; margin: 0px; width: auto;" for="ghx-trackingstatistic-none">None</label>
Issues will burn down their Story Points value upon completion.
<input id="ghx-trackingstatistic-remainingtimeestimate" class="radio" style="margin-top: 0px; margin-right: 2px; margin-left: 0px; padding: 0px; border-style: none; float: none; width: 15px; height: auto; vertical-align: middle;" type="radio" name="ghx-trackingstatistic" value="field_timeestimate" checked="checked"/><label style="float: none; display: inline; left: 0px; margin: 0px; width: auto;" for="ghx-trackingstatistic-remainingtimeestimate">Remaining Estimate and Time Spent</label>
Track time against issues using JIRA's Remaining Estimate and Time Spent fields. The Burndown Chart will be based on these two values.
</fieldset></form>

Work Log

Jon Smith logged work - 09/May/13 11:16 PM
  • <dl><dt>Time Spent:</dt><dd>1 day</dd></dl><dl><dt> </dt><dd>analysis</dd></dl>
John Smith logged work - 09/May/13 11:21 PM
  • <dl><dt>Time Spent:</dt><dd>4 days</dd></dl><dl><dt> </dt><dd>a</dd></dl>
John Smith logged work - 10/May/13 12:21 PM
  • <dl><dt>Time Spent:</dt><dd>1 minute</dd></dl><dl><dt> </dt><dd>test1</dd></dl>
<dl><dt title="Original Estimate - 2 weeks">Estimated:</dt><dd title="Original Estimate - 2 weeks">2w</dd><dd>
Original Estimate - 2 weeks
</dd></dl><dl><dt title="Remaining Estimate - 4 days, 7 hours, 59 minutes">Remaining:</dt><dd title="Remaining Estimate - 4 days, 7 hours, 59 minutes">4d 7h 59m</dd><dd>
Time Spent - 1 week, 1 minute Remaining Estimate - 4 days, 7 hours, 59 minutes
</dd></dl><dl><dt title="Time Spent - 1 week, 1 minute">Logged:</dt><dd title="Time Spent - 1 week, 1 minute">1w 1m</dd><dd>
Time Spent - 1 week, 1 minute Remaining Estimate - 4 days, 7 hours, 59 minutes
</dd></dl>
<label style="float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right; word-wrap: break-word;" for="timetracking_originalestimate">Original Estimate</label><input id="timetracking_originalestimate" class="text short-field" style="margin: 0px 5px 0px 0px; padding: 2px; width: 75px; color: #000000; font-size: 13px; max-width: 100%;" type="text" name="timetracking_originalestimate" value="2w"/> (eg. 3w 4d 12h)
The original estimate of how much work is involved in resolving this issue.
<label style="float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right; word-wrap: break-word;" for="timetracking_remainingestimate">Remaining Estimate</label><input id="timetracking_remainingestimate" class="text short-field" style="margin: 0px 5px 0px 0px; padding: 2px; width: 75px; color: #000000; font-size: 13px; max-width: 100%;" type="text" name="timetracking_remainingestimate" value="4d 7h 59m"/> (eg. 3w 4d 12h)
An estimate of how much work remains until this issue will be resolved.

Hi KP11,

I've taken a look at all your screenshots attached to TST-50391. The last attachment (https://jira.atlassian.com/secure/attachment/91868/Multi_Language%20-%20Agile%20Board%20-%20iBASEt%20Jira.pdf) appears to have a burndown (red) line and burnup (green) line, as you had originally wanted. So that appears to be working fine. Now for the screenshot MES_SAMPLING- AgileBoard- iBASEt JIRA.pdg (https://jira.atlassian.com/secure/attachment/91858/MES_SAMPLING%20-%20Agile%20Board%20-%20iBASEt%20Jira.pdf)--> you appear to have set the Estimation Statistic = Story Points but not actually estimated any of the issues - they show 0. Can you open up those issues and see if they do have Story Point values estimated? The field Story Points can be made visible on the screen by going into JIRA Administration and adding the field into the relevant screens (e.g. Default Screen) or another screen if you have customized your JIRA to use different screens for different issues types/projects. Let me know.

Joanna

We had to add the Story Point field. They were hidden and blank.

We are still trying to figure out if Linked Issues from parent issue are counted as subtasks and will show the estimated time.

We also assumed that adding another issue would not start a line at the bottom of the graph.

That was attached as the Multi_language board.

On the burnup (green) line we wanted to know why it started at the bottom. Teh user thought it would be higher up on the line. Do burnup lines always start at the bottom?

We added the story point field and will test.

No, the charts will not show linked issues. Only parent issues and sub-task issue types.

Also, remember that GreenHopper remembers various statistics at the START of the sprint. Everything after that - adding issues, estimating, removing issues - is considered SCOPE CHANGE. So in Burndown, your "Guideline" is based on the values at start of sprint. It won't change after that. Only burnup , burndown change.

So if you add an issue, or change estimate of an issue (story points or Remaining Time) or you create sub-tasks (and estimate those) *after* start of the sprint -- this is all considered scope change.

Do you know the difference between task hours and original estimate?

Looks like the estimate is based on task hours and not original estimate field that you enabled recently. It affects the graph lines as well. Guideline also looks off the slope base don the DOC definition

Is Task Hours a custom field that you have configured?

I just asked the Admin. Looks like it was created a 5 years ago!!!! So it should not have any effect!

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

13,152 views 15 13
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you