Due to the fact that the developer/manager to resolve/close a bug has to fill some specific fields (i.e. fixed_in_version), and that these fields appear in the form only pressing the resolve or close button and not is the generic bug update page, I guess it's better to forse the resolving/closing action just using those buttons removing the states from the list in the bug update page.

The proposal is to add to status list all the status below the resolved thresold plus the current status of the bug. In this way the user is forced to use the appropriate function (resolve or close button) to do the job.

The impact is just to add a new function (below attached) and to modify the bug_update_page.php and bug_update_advanced_page.php to call the new function instead of the old one.

function print_enum_status_string_option_list_no_closed_resolved( $p_enum_name, $p_val = 0 ) {
$t_arr = explode_enum_string( config_get( $p_enum_name.'_enum_string' ) );
$enum_count = count( $t_arr );
for ( $i = 0; $i < $enum_count; $i++ ) {
$t_elem = explode_enum_arr( $t_arr[$i] );
$t_elem2 = get_enum_element( $p_enum_name, $t_elem[0] );
if ( ($t_elem[0] < config_get( 'bug_resolved_status_threshold' ) ) ||
($t_elem[0] >= config_get( 'bug_resolved_status_threshold' ) && $p_val == $t_elem[0] ) )
{
PRINT "<option value=\"$t_elem[0]\"";
check_selected( $t_elem[0], $p_val );
PRINT ">$t_elem2</option>";
}
} # end for
}