How do you deal with verification / how do you use "Resolved"?

[Anthony Newnam]

I'm curious what "Resolved" means for other people. I've assumed this is supposed to mean that the issue should them be verified, normally be a quality team person. Is this how others use it? How should it be different than "Closed"?

If this is what it is supposed to mean, do you re-assign your issues to someone when they go to the Resolved state? If so, how does the person you re-assign it to keep track of what they should verify? JIRA seems to be geared towards hiding Resolved issues (though they could certainly have a custom filter).

[Ramiro Pointis]

Just to explain a little more. In our case, thanks that there are two Permissions ''Close Issue" and "Resolve Issue" we can ensure that the user that resolved the issue won't be the user that will verify if everything it's ok.

The developer does the modifications and the he 'Resolves' the issue, then comes the 'QA' user and verifies everything is good then 'Closes' the issue.

[Ramiro Pointis]

Or in a little more annoying way, it is assigned to the Project Leader and he is the one to decide to whom it would be assigned from the QA Role. Sometimes the clients... ;)

[Anthony Newnam]

When you move to 'Resolved', who do you assign the issue to?

[Ramiro Pointis]

To the user that it is the QA by Default. There's a Post-Function on the transition to configure this.

[Renjith Pillai]

Resolved, AFAIK, means the job is done, someone needs to verify. This could be the reporter itself, or someone as per your workflow requirement. There are many cases while the issue is automatically assigned to reporter or to someone specific while the issue is transistioned to Resolved.