My user is encountering this same issue: https://answers.atlassian.com/questions/62869/jira-agile-gadget-bug
However, I don't know that I feel the workaround the users are suggestion is a good one. Essentially, they're saying that you must have a fix version applied to each issue in order to get the burndown chart data to display correctly. However, the default behavior of JIRA is to not provide the field for specifying Fix Version until the issue is actually resolved. I agree with applying fix version ONLY when the fix is actually completed. It seems to be that forcing every issue to have a fix version so an agile gadget can display data is not a good idea. Is there a reason that the agile gadget modifies the filter query in this way? The user would love to be able to display a burndown chart on a dashboard but there's currently no good means for doing so. The other burn down options don't work properly and appear to be based on classic board data such as context. Also, the user does not want to display the burndown chart on a dashboard by version or fix version, but instead by sprint. This is how the rapid board burndown charts work, shouldn't the dashboards work this way as well?
Are there improved agile gadgets coming with updates to GreenHopper? What's the best way to get a sprint burndown chart listed on a dashboard?
Help would be appreciated.
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 a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG