Is this considered a bug or is it considered 'works as intended'?

I think that this is works as intended.

The $g_handle_bug_threshold is used as a coarse filter to allow access to the bug update page. From there, the access level to move the bug to any new state is determined by the $g_set_status_threshold array (by status) or the default $g_update_bug_status_threshold.

The assign to lists on both pages should come from the same routine with the same parameters, but the bug_update*_pages are missing the thresholds. Good catch...

In that case the comment in config_default_inc.php is somewhat misleading.

access level needed to be able to be listed in the assign to field.

$g_handle_bug_threshold = DEVELOPER;

This implies both the drop-down lists: in the update screen and next to the button 'Assign To:'.

However a related question, why is it possible without update permissions ( REPORTER) to change the status by means of a button, but not to change the 'Assign To:' also with a button. What is the intended difference.

See also 0004603 for an explanation what I am trying to achive.

Fixed in CVS.

Note that the assign_to list is valid for the "current" status only. That is, if the status and assign_to are changed simultaneously, it is possible that the new handler cannot access the issue. This is flagged as an error.

I went the wrong way with this fix. Those listed in the Assign To: dropdowns should have access level of $g_handle_bug_threshold.

Whether they can change the status is handled elsewhere. These two actions are independent.

Fixed in CVS again.

I downloaded from Mantis CVS Web 3 programs:

bug_update.php
bug_update_advanced_page.php
bug_update_page.php

however it still does not work as I expected.

I have set $g_handle_bug_threshold = REPORTER;
When I us the button 'Assign To:' the drop down list still only shows DEVELOPERS, however when I choose to update the issue ( possible while I set $g_update_bug_threshold = REPORTER; ) the drop down of the field 'Assigned to:" displays ( correctly ) all REPORTERS.

You also need to pick up core/html_api.php.

When using latest core/html_api.php I get an error on line 690, get_option_statuslist(). Perhaps I need to get more files form CVS. I will look into it this weekend.

If you have some suggestions, please let me know.

You also need core/print_api.php

Is this now resolved?

Yes, I did not respond to it while I was waiting for 0004648 to be solved. I see that you did resolve the problem, I will test it as soon as possible.