YellowGrass, currently only supports to comment on an issue when closing it. Although a comment can contain anything, user feedback suggested that more structure on resolution strategies would improve usability. Resolution strategies explain why the issue is closed (e.g. fixed, cannot reproduce). Which resolution strategies are the desired ones remains unclear, how to model them in a UI remains unclear as well. So far, we have collected:

• fixed
• wontfix (not sure this is really desirable)
• cannot reproduce
• incomplete

Suggestions for additional resolution strategies, or comments how to model them are welcome.

Submitted by Sander Vermolen on 16 February 2010 at 08:29