When a user X has not set the email_on_status flag a status change doesn't result in an email to that user. I guess that's the intension behind this flag.

In many cases a "status changer" also leaves a bugnote with the same update. Then no email is sent to user X regardless of the users setting for email_on_bugnote.

Here's why.

bug_update.php:

224         # Add a bugnote if there is one

225         if ( false == $t_bug_note_set ) {

226                 bugnote_add( $f_bug_id, $f_bugnote_text, $f_time_tracking, $f_private, 0, '', NULL, FALSE );

227         }

228

229         # Update the bug entry, notify if we haven't done so already

230         $t_bug_data->update( true, ( false == $t_notify ) );

Line 226 adds the bugnote but doesn't send an email due to the 8th parameter being FALSE!

Line 230 updates the bug itself.

core/bug_api.php->update(...):

if status has been changed

then call email_generic( $c_bug_id, $t_status, 'email_notification_title_for_statusbug' . $t_status );

This calls:

core/email_api.php->email_collect_recipients(...):

if $p_notify_type is undefined (a.k.a. status change)

and user has status_on_change = OFF

then drop him from list of receipients