View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0010122||mantisbt||bugtracker||public||2009-02-09 05:32||2016-07-11 15:36|
|Summary||0010122: custom_function_override_issue_update_notify not called when assigning a handler to reopened bug|
If a bug is reopened, the assign_to button is shown even if the bug is not yet in status assigned (resolution is reopened). This is not the case if a new bug is in status new, acknowledged or confirmed. Then this button is NOT shown.
Our custom function performs some action if the bug update changes the status to assigned or higher. This doesn't work if the assign_to button is used.
|Tags||No tags attached.|
In version 1.1.7 the bug_assign still doesn't call the function custom_function_override_issue_update_notify. Now the button "Assign to" is shown every time. Not as described above on reopened tickets only.
Solved this problem by adding the line
helper_call_custom_function( 'issue_update_notify', array( $f_bug_id ) );
I'm wondering if this should be closed as the customf function functionality pre-dates the plugin functionality that now exists.
In fact, I'd created a partial plugin previously to move some of the custom functions to a plugin so we could tidy up the source code.
Does anyone have any objections to removal the custom function functionality in git trunk for 1.3 and implementing a plugin for users who have legacy code.
Assuming we really want to remove custom functions (something I don't have time to think about atm), it would in any case be in scope of a 2.x release as we would potentially break a lot of installations with that.