The described behaviour is true.

The list of items with boxes is coverned by the read-only threshold. Each command in the list is not gated by the user's access level. However, when you submit the page to take the appropriate actions, a detailed check is done on each issue to ensure that it meets the access criteria. An informative message is prin ted for those that don't meet the criteria for the action.

I do not understand you explanation fully. I expect to see a informative message whenever I choose status for an issue which I am not allowed to. This when you are updating form the dropdown box next to 'Select all'.

However when I am testing I do not get the informative message but the status is just changed, to a status I am not supposed to.

When I use the button/dropdownlist 'Change Status To:'or when updating the Status field I am only allowed to choose an appropriate status according to $g_set_status_threshold.

Is this anyhow related to 0004602, which also has different views on the Assign To?

Maybe I should explain what I am try to accomplish.

Whe have reporters who are only allowed to report issues and to resolve their on issues. However a HeadOfDepartment ( = Developer ) should be able to change status in between: acknowledge, feedback, progress, testresult.

So reporter should only change status to 'resolve'. Further the should be able to assign the issue to anyone ( prefferbly a developer ). The developer should be able to assign the issue to anyone ( could be the reporter ) for feedback.

Can anyone verify this behaviour?

I'm not sure what I was thinking about with my first response... (not enough caffine).

I added some comments to 0004602 and fixed the inconsistency (twice).

The statuses listed in Change Status To are valid for the current user. The Assigned To list should come from the $g_update_bug_threshold.

You should be able to accomplish what you want by setting:

$g_update_bug_status_threshold = REPORTER;

$g_set_status_threshold = array( ACKNOWLEDGED => DEVELOPER, CONFIRMED => DEVELOPER, FEEDBACK => DEVELOPER );

Is there something like a $g_update_bug_assign_threshold ?

I want reporters to assign an issue to any other reporter. The change of status is already covered with $g_set_status_threshold = array(..).

I want reporters not to update isssues, but only change status an/or assign to, by means op the buttons.

The visibility of the "Update" button is controlled by $g_update_bug_threshold. As you have also noted, this controls the listing of a user in the Assign To: list.

I believe that this is a feature request to separate these two items.

Feature request captured in 0004648