Assigning a defect to a QA

[srouleau]

Hello,

We've been using Mantis for a while now, and have been using only the following states: New, Assigned, Feedback and Resolved. Only recently have we started systematically closing defects, and thus are starting to use the Closed state. It works great when there's a single QA in charge of closing all the bugs, but we've recently entered crunch mode, and everyone has been pitching in to close defects. We don't necessarily have the reporter close the defect, it's whoever can, as long as it's not the developer who fixed it.

Someone had the good idea of re-assigning the defect to himself to notify the others "I'm looking at it to close it", and in the process gave me a heart attack (ie: it looked like he had re-opened a showstopper defect 4 days before our ship date).

I've searched the forum for something similar, and a few hits came up but I could not see a resolution. Surely there must be a better way to assign queue defects for closing without re-opening them? Besides, I'd rather not re-use the 'assigned to' field, as I'd lose the quick way of knowing who fixed it.

We're currently using 1.1.7...

Thanks,

Stephane

[simone.girlanda]

We have the same process workflow, we choose to to add a new status (QAcheck) before closing and assign bugs to a QA user to check & close them.
In this way we lost developer information from bug, but we are planning to add a custom field to store developer_id.