We use Jira 5.1.4/Jira Agile 6.3.2.2 and I can see the Jira Rapidboard burndown charts for a sprint in the list of gadgets, but I do not see anything to show me a burndown chart for a whole version, as opposed to a sprint.
This seems like a basic requirement, seeing as there are no GANTT charts built into Jira. Am I missing something?
How else could I get a quick and easy visual health check on my release?
So, the Agile Classic Hour Burndown Chart gadget does actually work now that I have added a start date to the version. Without the start-date, the chart was blank.
I am a bit uncomfortable about using classic board gadgets as I understand they will eventually be de-supported. It would be good if this feature made its way into the main supported product sets.
Looks like you are referring to this feature request : https://jira.atlassian.com/browse/GHS-8829. Apparently, this has been marked as 'wont fix' which means that Atlassian developers are currently not working on this requirement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have a list of the reports available, there should be a Version Report listed about halfway down. As long as the issues in sprints have versions assigned, then this should provide the view you are after.
Is this the sort of thing you are after?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the suggestion. This would be good if:
1) it showed the time spent. The estimated completion date does not work well for us because Velocity is not very useful because we have a lot of tasks In Review and not yet Closed/Done.
2) there was a widget to show this on the dashboard
There is a widget for The Agile Classic Hour Burndown Chart, but this doesn't show much for me for some reason, as I am using the Rapid Boards instead of Classic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If your board's estimation metric is effort, the version report is based on original effort and doesn't reflect remaining effort. This is why a version burndown, comparable to the sprint burndown, which would show a trend based on remaining estimated effort would be interesting.
-David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.