-
Suggestion
-
Resolution: Answered
-
None
-
None
The Agile Gadget is great, but I need to have the ability to separate the "Info" and "Issues" tabs and the "roadmap" progress bar onto 3 separate gadgets.
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-2516] Issue burndown chart gadget
Pasted from here (hope this is the right place for it):
When do you plan to implement a task burndown chart plus the wallboard gadget for it?
I am asking this because we have to move our scrum teams to the new scrumboard by November. It is a process, and we can't wait until the Classic boards will be unavailable.
The biggest pain currently is the lack of task burndown chart and the wallboard gadget for it. On the classic board we were able to show this with a context filter. This is heavily used on the meetings.
Right now we only see the story point based chart witch is good, but the Product Owners usually accept the stories at the end of the sprint. So the Story point based chart does not tells much about the current progress.
Taking a look at jira.atlassian.com's greenhopper scrumboard: it does not use Story swimlanes so movement of stories indicate the work better, but this is not the ideal scrum setup. As not being a dogfood, maybe it is not that painful for that team. For the story swimlane users (which is the default setting) it is a real problem.
We actually create fixversions for the sprints on the new boards and try to syncronize the assigned issues with the issues in the sprints so we can see the Task burndown on the Classic board.
Please comment/like if this is affecting you!
Laszlo Kremer
added a comment - - edited Pasted from here (hope this is the right place for it):
When do you plan to implement a task burndown chart plus the wallboard gadget for it?
I am asking this because we have to move our scrum teams to the new scrumboard by November. It is a process, and we can't wait until the Classic boards will be unavailable.
The biggest pain currently is the lack of task burndown chart and the wallboard gadget for it. On the classic board we were able to show this with a context filter. This is heavily used on the meetings.
Right now we only see the story point based chart witch is good, but the Product Owners usually accept the stories at the end of the sprint. So the Story point based chart does not tells much about the current progress.
Taking a look at jira.atlassian.com's greenhopper scrumboard: it does not use Story swimlanes so movement of stories indicate the work better, but this is not the ideal scrum setup. As not being a dogfood, maybe it is not that painful for that team. For the story swimlane users (which is the default setting) it is a real problem.
We actually create fixversions for the sprints on the new boards and try to syncronize the assigned issues with the issues in the sprints so we can see the Task burndown on the Classic board.
Please comment/like if this is affecting you! 
Rich Ellis
added a comment - Yes, please! We are using the "GreenHopper Hour Burndown" chart gadget on a Confluence page to give a simple and clean look at the burndown. The Agile Gadget is way too busy and has too much UI chrome. But, we have a few projects that aren't estimating hours and are just tracking tasks. It would be great to have the simplicity of an Issues Burndown chart.
Rich Ellis
added a comment - Yes, please! We are using the "GreenHopper Hour Burndown" chart gadget on a Confluence page to give a simple and clean look at the burndown. The Agile Gadget is way too busy and has too much UI chrome. But, we have a few projects that aren't estimating hours and are just tracking tasks. It would be great to have the simplicity of an Issues Burndown chart. 
Julia Wester
added a comment - and make this wallboard capable please? We don't use hours that often. I am severely lacking the issues burndown gadget that is wallboard capable. Seems like it would be so much like the hours burndown so maybe not a lot of overhead to provide.
Julia Wester
added a comment - and make this wallboard capable please? We don't use hours that often. I am severely lacking the issues burndown gadget that is wallboard capable. Seems like it would be so much like the hours burndown so maybe not a lot of overhead to provide. 
This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work.
Regards,
GreenHopper Team