View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007104 | mantisbt | bugtracker | public | 2006-05-17 11:00 | 2011-12-14 03:18 |
Reporter | mcraig88 | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 1.0.1 | ||||
Summary | 0007104: Auto assign on resolve | ||||
Description | There should be a way to get Mantis to reassign an issue to it’s opener. I just did the following, which seems counter intuitive.
| ||||
Tags | No tags attached. | ||||
Did you consider setting the following option to OFF: Automatically set status to ASSIGNED whenever a bug is assigned to a person.This is useful for installations where assigned status is to be used whenthe bug is in progress, rather than just put in a person's queue.$g_auto_set_status_to_assigned = ON; |
|
Also probably such "verification" is more correct to do using a special issue status that reported can change. This way it won't be lost who actually fixed some issue. |
|
You wouldn't lose 'who fixed an issue' because the Issue History, traps when the status changes from Assigned to Resolved. vboctor: I don't think that variable is what I'm looking for. I think this is more of a workflow problem. When a bug is assigned to a developer, it needs to be fixed. When the problem is fixed and ready to be tested, the developer sets the status to Resolved. The person that filed the issue should be the one to verify that the problem is fixed to their satisfaction. Once they are satisfied, the issue is then closed. |
|
Now that I think about it, how about setting up a variable like: That would do it, with the requisite code of course. |
|
I know this is an old, unwanted issue, but I would love to see an Auto-Assign on Resolve feature. Second-best would be to add an Assign field to the Resolve form. |
|
As I just wrote in 0006418, such a field does exist in 1.2.x |
|
Great. I'll get on my guys to update. We're currently running 1.2.0rc1 and it's not there. |
|
Yep, this was fixed in 1.2.0 (see 0003391) |
|