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?
Here's what's happening:
This is GH 5.8.4.
First of all, I'm going to introduce myself. My name is Gorka, I work as product manager in Appfire Although this is my first public article in the community, I've been around since 2013. I starte...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events