Please note that while this issue has been resolved in 5.6.0 the status will let you know whether it has been Fixed, Answered, Obsolete or Won't Fix.

Cumulative Flow Diagram as used for software development.

This would be huge. What this really comes down to is being able to burn down on ANY or ALL statuses. This would make the chart into something really useful, an example of a "Cumulative Flow Diagram". See http://edn.embarcadero.com/article/32410 for more details on such charts in software development. As it is, I can only burn down on "done" right now, but often our issues must go into a Verify bucket, and they get marked as Done at very irregular intervals. That SEVERELY compromises the utility of the burndown for us.

See cfd006 attachment for a good example of a CFD. (Drawn there as a burnup, but easy to reverse).

Yeah, we used to draw something like that too - very useful to see
1) Work in progress versus not started (so you can easily see people who may be taking on too many tasks at once)
2) Work added or removed from the sprint (after negotiating with the product owner)
3) Takss for completed stories (which is different than tasks done but the story is still not yet done because 1 task remains)