バーンダウン チャートの表示

Is there any plan to include some of the other indicators that are currently on the "old" agile burndown, such as team effort and estimate accuracy? Those are crucial indicators for us.

When I refresh Report page in browser the time estimates are in weeks, days, hour e.g. 5w 3h 30m

I have to navigate to Work and back to Report to get a meaningful time estimate in hours e.g. 191h

Is this a bug? I want to keep the estimate in hours.

This is annoying - like much of the Rapid Board there is no configuration for this. I would like to turn off the Time Spent line as it's usually the inverse of the Time Remaining and confuses people who don't need to see it. I also keep an excel chart of the burn down because I cannot read the time remaining at the end the day from the graph. I would like a large point plotted for each day with a visibility toggle and a bubble that reads Time Remaining, Ideal Time Remaining (the guideline value at this point, and the Delta.

What actually affects the red line on the burndown chart?

If a sub-task of a story was estimated to take 10 hours and it only took 3, and the issue is resolved, does GreenHopper automatically reduce the red line by the remaining 7 hours? Or does it only reflect the 3 that were logged?  Do I have to manually log the last 7 hours to reduce it to 0?

Hi, I'm trying to understand where the value for Remaining Time Estimate column comes from. I've started the sprint and one of the task says it has 266.5h in that column. However, when I open the task I see that Original Estimate is 4d, Remaining is 4d and Logged is 4d 2h 30m.

Thanks.

I didn't find a good way with the RapidBoard to show the global state of the project.

The perfect view will be a global/release burndownchart (not based on a sprint but on a version)

Ideally I would like to give either the start date, the end date and if the tasks are not already identified at least a start global estimation (either in story points or in original estimate time).

A release burndownchart would help the PO and the team to see if at the global view the project is going well.

On this kind of chart it can be interesting to see appear the sprint frequency just to say the release will be done in N sprint.

Is there any chance this kind of feature will appear in GreenHopper or maybe I missed a rapidBoard functionnality ?

Hello.
Don't you have a plan merging some feature of "Classic burn down chart" to rapid board's burn down chart?

I like these functions and hope we can use them as same as classic chart board.

• Filtering feature (Actually, we draw and use each members' burn down chart)
• "Required Daily Burndown Rate"(Orange line), and "Estimate Accuracy"(Yellow line)
• Holiday setting (It seems current Bingo filter display all days (contain Saturday & Sunday) to X-axis)

I've successfully added tasks to a new sprint.

In report mode, in burndown chart, I cannot see the diagonal grey "Guideline". It is present in the legend but it's nowhere to be seen on the chart itself.

I used to work on JIRA + GH but that was a long time ago and it seems that things have changed. I browsed the GH 101 documentation.

I do not recall setting up the effort (how many people will work) for the sprint, maybe that has something to do with it (although I don't think so)?

Your help will be greatly appreciated.

I have a status/column called "Ready To Deploy", how do I set it up so that the burndown chart will treat as done...  Right now the chart remaining values remains way above the guideline until we deploy and close all the issues...

Is there a plan to configure or at least add more columns for the detailed report under burndown chart? So far it has just task IDs and amount of hours reported, but doesn't state task headline and who updated the estimate. It makes usage of this table very inconvenient, I need to click on each task and open it in new tab for understanding the details.

Can we use issues on the burndown chart?  I know traditionally a measure of effort is used (points / hours).  But I'm looking for an issue burndown representation.  The Classic board had it.

Vote +1 for Hourly Effort Burn-down Charts please.

I really appreciate the burndown chart, be it for issues or based on story points - what i do strongly miss, though, is a way to display the charts for already closed sprints, e.g. for velocity considerations.

The only way I found to proceed here is to define a filter for a closed sprint to at least see all the covered user stories/tasks, and then sum up the story points 'by hand' - is there an easier way for that? This is very important from a planning perspective.

Hello.

How can I load epic numbers in the sprint drop down field?

I would like to know the story points that are completed /remaining for an epic, is there any other way to view this in the chard board?

The guideline is missing in my burndown chart, anyone know how to make greenhopper render it?
I'm using greenhopper 6.0.6.

Regards,
Mikael 

Hi All,

In the burn down chart is there a way to view the comments entered when entering the time worked.

Thanks

Tony.

Do the charts include data for isues that have a status of "closed?"

Adding filters to this report would be hugely helpful.  We want to see burndown charts for individual employees as well as the entire team.

I'd like to be able to burndown unscheduled tickets (I shouldn't be forced to created a backlog fix version).

I have an issue with sub-issues in a sprint. The parent issue has the story points field set to 0, while sub-issues has the actual values. This way of doing it worked fine in the classic version of the burndown chart, but in the updated version this set of issues count as 0 points. What I would expect was to see that subissues count against the total score as I finish them, but at it is now, they aren't even shown in the graph. Is there a best practice i've missed for this problem?

The Burndown Chart keeps track of the added and removed issues from the sprint.
Do we have access to this data from the issue navigator?
I'd like to display an Filter Results gadget with added issues and removed issues, but whatever i try, i only get 'sprint field does not support historic searches'.

If I add time to an issue via 'Log work' and chose a different date than the one given in 'Date Started' the time is not used in the Burndown Chart nor listed in the list below the chart.

Is this how it should be and in that case why? It messes things up if people forget to report time when they should.

The particularely unuseful feature of the burndown chart is in the list of stories beneath. It only shows the ID's but it'd be useful to have the summary field displayed.

The 'Scope change' column is also redundant due to the 'Event' field, surely?

I expect not everyone would agree so I'd suggest the best option would be to allow some level of customisation for what columns are displayed in this report.

When does the burndown, acualy burn down. And is there a way to change when it does it. Ie. we have the collums open > in progress > code review > test on dev > test on test > done. It only burns down on done. But the dev team i mostly done when it is at "test on dev", and we would like for it to burn down here. But again we would like to keep the QA tracks for testing as sometimes they can't test because it is technical, and the dev. has to test it, and move it. Otherwise they forget.