This is possible to do unless the version has been released, in this case the fixVerison is essentially hidden. I found this frustrating from the point of view, as you say, of looking at historical burndowns on an individual basis.
Since fixVersion is no longer used in GreenHopper 6 this funtionality will not be changed. The new way of organising Sprints via the new Sprint field allows one to see historical burndowns.
However, if you have a setup where your backlog is the parent of the fixVersion you can open a Statistics burndown chart by children to see the historical burndown as a series of historgrams.
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs