I personal understand the life cycle of a issue like this:
- Create an issue. - Assign an issue to a developer (optional) - Resolve a issue as soon someone start to work on this issue - Close the issue as soon the patch is in the sources
I'm used to not resolving them until they're fixed. See, e.g.:
http://issues.apache.org/bugzilla/page.cgi?id=fields.html#resolution
If you have a test group, then they're not closed until they've been verified, but, without a test group, we just close them as they're fixed.
Does Jira have different conventions?
Doug
