Actions
Feature #9744
closed
permissions per project
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Invalid
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.
Updated by Etienne Massip over 12 years ago
- Status changed from New to Closed
- Resolution set to Invalid
Yes, roles are designed to handle different permissions on projects for the same user.
I guess you are confusing roles with groups.
Actions