Patch #13545


Workflow permissions are broken if user has multiple roles in project

Added by Alexander Kriventsov over 10 years ago. Updated over 10 years ago.

Needs feedback
Issues workflow
Target version:
Start date:
Due date:
% Done:


Estimated time:


If user has multiple roles in project workflow permissions don't work.
It works in two cases:
  1. User has one role
  2. User has two roles with the same workflow permisions


issie_permissions.diff (846 Bytes) issie_permissions.diff Alexander Kriventsov, 2013-03-21 14:50
r1.png (45.5 KB) r1.png Alexander Kriventsov, 2013-03-22 14:55
r2.png (45.4 KB) r2.png Alexander Kriventsov, 2013-03-22 14:55
members.png (11.4 KB) members.png Alexander Kriventsov, 2013-03-22 14:55
good.png (24.8 KB) good.png Alexander Kriventsov, 2013-03-22 14:55
members2.png (11.2 KB) members2.png Alexander Kriventsov, 2013-03-22 14:56
bad.png (25 KB) bad.png Alexander Kriventsov, 2013-03-22 14:56
Actions #1

Updated by Daniel Felix over 10 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. :-)

Actions #2

Updated by Alexander Kriventsov over 10 years ago

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.

Actions #3

Updated by Dipan Mehta over 10 years ago

I figured by try an error what would be the ultimate behavior of the particular field when multiple roles are at play:

  1. Required: the field will be FORCED to be required only if ALL ROLES requires it.
  2. 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