View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014832 | mantisbt | bugtracker | public | 2012-10-15 18:57 | 2017-01-18 17:14 |
Reporter | egelvin | Assigned To | |||
Priority | high | Severity | feature | Reproducibility | always |
Status | confirmed | Resolution | open | ||
Platform | Windows | OS | Windows | OS Version | Windows 7 |
Product Version | 1.2.11 | ||||
Summary | 0014832: When resolving an issue, developer is assigned even when "assign to" is left blank | ||||
Description | When resolving an issue, if no option is selected for "assign to", the developer still gets assigned when clicking "resolve" | ||||
Tags | No tags attached. | ||||
Behavior is confirmed. The setting of handler is done by bug_resolve() function, when the handler_id is null/0, in which case the function sets it to Current User when resolving the issue. As far as I can tell, this is intended behavior, although I guess the valididty of this design is debatable, and in any case the fact that bug_change_status_page.php allows the user to set the handler to blank, and that choice is then overridden by bug_resolve() is not consistent. There are two approaches:
|
|
I am definitely in favor of the second alternative "revise design". Would it be a solution to change the line if( null == $p_handler_id ) { in bug_resolve to if( null === $p_handler_id ) { Or is there any problem with bug_actiongroup.php when you change the code like this? I tried at least every case that came to my mind when resolving via bug_change_status_page.php, and there were no problems from my point of view. Cases I tried:
|
|