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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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