Reporter definitely needs an ability to reopen bugs and probably close bugs. This is a good rule to allow original reporter to check again it bug is closed.

Though in this case there appears to be no difference between tester and reporter.

We have the same problem to define our QA-workflows.

This is currently a problem in Mantis, because the user levels are hierarchically, that means a user of level 4 may do everything users of level 1,2 and 3 may do (plus some more rights).

To solve such a request sufficiently, I guess you would need two arrays similar to the $g_status_enum_workflow array, defining

• which user level may edit which bug states
• Which user level may assign which bug states

e.g. (UPDATER is the project board, that decides, which bugs have to be fixed and gives priorities; MANAGER is used as "review authority" to check if a bug has really been fixed)

$g_UserEditStateRights[REPORTER]= '10:new,20:feedback';
$g_UserEditStateRights[UPDATER]= '10:new,20:feedback';
$g_UserEditStateRights[DEVELOPER]='20:feedback,40:confirmed,50:assigned,80:resolved';
$g_UserEditStateRights[MANAGER]= '80:resolved';

$g_UserSetStateRights[REPORTER]= '10:new';
$g_UserSetStateRights[UPDATER]= '20:feedback,30:acknowledged,40:confirmed,80:resolved';
$g_UserSetStateRights[DEVELOPER]='20:feedback,50:assigned,80:resolved';
$g_UserSetStateRights[MANAGER]= '20:feedback,50:assigned,90:closed';

The threshold 'rights' suggestion I think still applies to the current releases.

Implementing this would probably mean we could simplify number of configuration variables controlling "who can do what" in the config.