We're using GreenHopper's Agile Gadget to show a burndown chart for our upcoming release. This works fine for a default workflow, where issues transition from Open through Resolved to Closed. The bug is considered "done" on the burndown chart when it hits the Resolved state. (I read this somewhere, but can't find it now.)
But we've configured our workflow so it looks like this:
Resolved -> Verified -> Closed
In this case, the burndown drops when the bug hits Resolved, then actually rises when it hits Verified, before dropping again at Closed.
Is there a way to configure the Agile Gadget (or GreenHopper itself) so the burndown behaves correctly at these custom workflow steps?