I guess the correct behaviour in this case is dependent on the process you are using. For some users the fact that a new bug is submitted is more critical than when one is assigned, hence, they might have the managers notified of new bugs, but not when they are assigned.

Also the main action was to submit the bug, rather than assign it.

OK, agree, this is a mostly process of using bugtracker. Generally I would like to have the following behavior:

1. when bug is added, all managers are notified always
2. if bug is not assigned, all developers are notified also so one of them can take care on this bug
3. if bug is assigned on adding, only assigned developer is notified

quite logical, I think. Current notifications schema doesn't allow to set up this, so let's put this on shelf as a possible feature for future releases.

Thank you.

edited on: 08-20-03 15:14

I'm raising this again. Is it possible to make a configurable option to change this?

The solution is simple. Here is what I've done in core/email_api.php in function email_collect_recipients() :

$t_notify_type_for_threshold = $p_notify_type;

this code should be switchable in config file

if (config_get( 'bug_assigned_is_higher_than_new' ) && $p_notify_type == 'new')
{
    if (intval(bug_get_field( $p_bug_id, 'handler_id' )) != 0)
        $t_notify_type_for_threshold = 'assigned';
}

end of switchable code

$t_threshold_min = email_notify_flag( $t_notify_type_for_threshold, 'threshold_min' ); // was $p_notify_type instead of $t_notify_type_for_threshold
$t_threshold_max = email_notify_flag( $t_notify_type_for_threshold, 'threshold_max' ); // was $p_notify_type instead of $t_notify_type_for_threshold