How to restrict assignment power on a single project

mark100net · Post by **mark100net** » 29 Jul 2005, 17:02

Version 1.0.0a3

I have the default setup where most "developers" can assign bugs on all projects on which they are developers.

But I have one project where I want only managers or admin to be able to assign.

So with that project selected I went to manage_config_work_threshold_page.php and unchecked the box in the "developer" column on the "Assign an Issue" row.

I would have thought that this would now prevent a "developer" from assigning bugs in this project (but only in this project). But a developer user can still assign bugs in this project (whether or not they are added as a developer to the project).

What am I missing?

Thanks,

Mark

thraxisp · Post by **thraxisp** » 29 Jul 2005, 18:11

This works for me. Was the right project selected at the top of the manage page?

mark100net · Post by **mark100net** » 29 Jul 2005, 19:49

Yes, when in the manage page, the correct project is shown in the drop down in the upper right, and the note to the effect that this action will only affect the Restricted project is shown in bold at the top. When I uncheck the box in the developer column in the "Assign Items" row, the table cell around the box turns green (presumably indicating that this setting overrides the global setting). The developer user is nevertheless able to assign items in that project, but ......

I just noticed that it depends on which project the developer user has selected while viewing the issue. If I (while logged in as the developer user) have "All Projects" selected in the upper right, and I view an issue in the restricted project, I can assign the issue. But if I have the restricted project selected while viewing the same issue, I cannot assign it (there is no drop down to do so).

Is this how it is supposed to work?

Thanks,

Mark

thraxisp · Post by **thraxisp** » 30 Jul 2005, 12:10

You've found #5969. This has been fixed and will be in the next release.