View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0018032 | mantisbt | feature | public | 2015-01-19 03:17 | 2015-01-29 06:12 |
Reporter | L_Aleman | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0018032: New Feature wish: Auto re-assign to category owner on re-open | ||||
Description | Dear Mantis Developers, If possible, I would like to see a setting that auto assigns a reopened Issue to the assigned "category-owner". Similar to the settings that auto assigns issues to a category owner for new issues. Kind regards, | ||||
Tags | No tags attached. | ||||
Thanks for the suggestion. The current reopen behavior is to change status to 'feedback' (which I think does not make sense, because that is generally understood as requesting info from the original reporter). I have it on my todo list to change to 'assigned' at some point, which basically means the last person who handled the issue becomes responsible for dealing with reopen request. I would be interested in knowing the rationale behind your request, i.e. why you would want the assignment to change based on category. |
|
|
|
Hi, the rationale is that we have a dispatcher. That checks all newly opened issues, and should check all reopened issue. Right now, Reporters are not allowed to assign issues. Reopened issues stay with whoever was the last handler of such issue, therefor our dispatcher needs to check for reopened issues frequently. If we set the status to NEW_ then it would mean the dispatcher needs to check the history of each issue. |
|
@atrol thanks for the clarification. I am not really sure 'NEW_' is a good default, IMO 'ASSIGNED' makes more sense. Reopened issues would have a resolution of 'reopened', so it should be quite easy for your dispatcher to use a filter based on that to quickly identify the issues, regardless of the status (which implies of course that when re-resolving issues, the resolution code is changed again the the correct value). If that is not good enough, you always have the option to create a custom 'REOPENED' status code [1] and set $g_bug_reopen_status = REOPENED [1] http://mantisbt.org/docs/master-1.2.x/en/administration_guide/admin.customize.status.html HTH. |
|
We did create the custom Status "Reopened" and yes, we filter by it. However it means that someone needs to continously look for reopened issues. we were hoping to get the Auto Assign functionality, this why the dispatcher could also get an email notification that the issue was reopened and assigned to him/her.... You know user. The always want the system to do everything for them ;o). |
|
I was able to somewhat satisfy my users with a workaround. Here the code: $c_filter['reopened'] = array( |
|
Glad to hear you found a workaround. |
|