How to configure what GreenHopper considers "done"?

[Joel Parker]

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?

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You can do it under Task Board settings: http://confluence.atlassian.com/display/GH/Configuring+your+Task+Board+Settings

[Joel Parker]

The Task Board settings was the answer. Thanks for the help!

[Joel Parker]

Here's what's happening:

1. Open
   Burndown shows "To Do 10 / In Progress 9 / Done 86"
2. Resolved (Resolution: Fixed)
   Burndown shows "To Do 9 / In Progress 9 / Done 87"
3. Verified (Resolution: Fixed)
   Burndown shows "To Do 9 / In Progress 10 / Done 86"
4. Closed (Resolution: Fixed)
   Burndown shows "To Do 9 / In Progress 9 / Done 87"

This is GH 5.8.4.

[Renjith Pillai]

Are you setting the Resolution in the post functions in the workflow while moving to 'Resolved', clearing it when it moves to 'Verified' and then again setting it when it moves to 'Closed'?

[Renjith Pillai]

And looks very similar to the discussion ongoing here