Thanks for the very descriptive bug report. I'll look into fixing this ASAP.

No probs, thanks dhx. I patched my site by modifying html_api.php:html_button_bug_change_status():

    # resort the list into ascending order
    ksort( $t_enum_list );

    # Get the default selected option as the next highest available status
    # Otherwise fall back to using the last element in the array
    end( $t_enum_list );
    $t_default = key( $t_enum_list );
    reset( $t_enum_list );
    foreach( $t_enum_list as $key => $val ) {
            if( $key > $t_bug_current_state ) {
            $t_default = $key;
            break;
        }
    }

back to essentially the same code from 1.1.6:

    # resort the list into ascending order after noting the key from the first element (the default)
    $t_default_arr = each( $t_enum_list );
    $t_default = $t_default_arr['key'];
    ksort( $t_enum_list );
    reset( $t_enum_list );

I was also thinking of setting up $g_status_enum_workflow in config_defaults_inc.php so we have sane default statuses for each stage of the default workflow.

I don't think the first status in the workflow was ever meant to be the default... it just worked out that way by chance. But now you mention the possibility, I like it, and will document it as a feature :)

We'd just need to remember to ksort() the enum list in some special cases as it can no longer be assumed that the status enum setting is linear (lowest status to highest).

I think it was an intended "feature" that was sort of forgotten about at the time that the option was commented out of the config_defaults_inc.php and started to live in the database.

So new Mantis installs after that point would have defaulted to the first available status and required people to use the Workflow Transitions page to set their desired defaults, while existing installations would already have it configured in the config file and worked fine until upgraded to 1.2.1.

I agree that reverting 0011729 and setting up sane defaults in the config is the ideal solution for both new and upgraded installs.

Thx djcarr for the workaround, works fine :)

We have found here the same situation
Taking the config_inc.php here

$g_status_enumworkflow[NEW] ='50:assigned, 20:feedback';
our expectation it will show in the dropdown first Assigned and as second feedback (this is the way it worked in 1.1.x

Will this be fixed in mantis 1.2.2?

@jreese: thanks for handling the revert.

This regression should be fixed in 1.2.2 but will need some further improvement in 0012089 to clean up this part of the code base. In particular, documentation of this functionality is important. I'll handle it as it's not urgent :)

Revert committed to 1.2.x and master branches.