It would good if one could do work flow e.g. have product Manager (defining priorities (which version/patch it should appear in), closing issues etc), they would pass it on a support manager to delegate to thier staff to validate and resolve (if resolved it would be go back via the support manager to the product manager, they do not do bug fixes) or pass on to the development manager who would delegrate it to testers and developers. A bug should not be marked as resolved unless the code changes have been tested. Then it will go back via the development manager to the support manager (who may need to install it on site to finally resolve the issue) and then finally to the Product manager who will close the issue.
Hannes van Wyk
Actually our method is that a bug can be marked as "resolved" as soon as the developer thinks it is fixed, but it should not be CLOSED until QA has confirmed it.
Fog Creek Home