We are having issues in the burndown chart.
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-22822Scope changeIssue added to sprint
09/05/2013 23:15FND-22801Scope changeIssue removed from sprint
FND-22641Scope changeIssue removed from sprint
FND-21904Scope changeIssue removed from sprint
FND-22806Scope changeIssue removed from sprint
FND-21967Scope changeIssue removed from sprint
09/05/2013 23:16FND-22822Work logged1d logged, Remaining Time Estimate changed from 2w to 1w 4d
09/05/2013 23:21FND-22822Work logged4d logged, Remaining Time Estimate changed from 1w 4d to 1w
10/05/2013 12:21FND-22822Work logged1m logged, Remaining Time Estimate changed from 1w to 4d 7h 59m
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*
|<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
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.
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;">
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.
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
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events