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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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