Patch #13545
open
Workflow permissions are broken if user has multiple roles in project
Added by Alexander Kriventsov over 11 years ago.
Updated over 11 years ago.
Description
If user has multiple roles in project workflow permissions don't work.
It works in two cases:
- User has one role
- User has two roles with the same workflow permisions
Files
- Category set to Issues workflow
- Status changed from New to Needs feedback
Please describe, what you mean with "don't work".
Can you give some testcase? This would help us to test what your talking about. :-)
I will try, but my English is not so good...
I have two roles R1 and R2.
I have for R1 and tracker "Bug" start date is requiered for state "New".
When I apply for user "test" role R1 everything are working.
But when I add for user "test role R2 in the same project permissions are not working.
Please take a look in attachments.
I figured by try an error what would be the ultimate behavior of the particular field when multiple roles are at play:
- Required: the field will be FORCED to be required only if ALL ROLES requires it.
- Read-only: the field will be FORCED to be read only if ALL ROLES makes it read-only.
If the field id NOT REQUIRED for any role - (e.g. as reporter role don't have to fill target-version) it will not force you to be REQUIRED.
If the field is NOT READ_ONLY for any role - (e.g. as a manager role I can see the 'Resolution' and update it) it will not force you to be READ_ONLY.
So in general multiple roles makes it 'more permissive'.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
