ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
permissions per project (Feature #757)
Description
Maybe I'm missing something but when setting permissions I can't set different setting for the same role in another project:
for example , I want that in project "A" a developer can set issues public or private but in project "B" he can't.
Do I have to create a new role for this scenario?
It will be very helpful if it could be implemented.
Associated revisions
Trac importer: support database schema for Trac migration (#757 by John Goerzen).
git-svn-id: http://redmine.rubyforge.org/svn/trunk@1195 e93f8b46-1217-0410-a6f0-8f06a7374b81
History
Updated by Holger Just at 2011-12-07 12:53 pm
Yes, you need to create a new role for that. Each role defines a set of granted permissions that can be applied to a project membership. If you want different sets of permissions, you need to create different roles. This is how role based access control (RBAC) works everywhere.
Note that a single user can have multiple roles in a project. The resulting permission sets are added. You can also have an arbitrary number of roles defined in your ChiliProject. Now roles can be created from the Administration -> Roles and Permissions screen.
- Status changed from Open to Closed
Updated by eyal R at 2011-12-07 12:57 pm
Thanks for the detailed answer