Patch #13545
Workflow permissions are broken if user has multiple roles in project
| Status: | Needs feedback | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues workflow | |||
| Target version: | - |
Description
It works in two cases:
- User has one role
- User has two roles with the same workflow permisions
issie_permissions.diff 
(846 Bytes)
r1.png (45.5 KB)
r2.png (45.4 KB)
members.png (11.4 KB)
good.png (24.8 KB)
members2.png (11.2 KB)
bad.png (25 KB)
History
#1
Updated by Daniel Felix over 9 years ago
- 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. :-)
#2
Updated by Alexander Kriventsov over 9 years ago
- File r1.png added
- File r2.png added
- File members.png added
- File good.png added
- File members2.png added
- File bad.png added
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.
#3
Updated by Dipan Mehta over 9 years ago
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'.