Query related to RTC Roles and permissions
We are trying to assign "Prevent Editing" operation behavior for a particular Role (for example Team Member). When a user is assigned a Team Member role only, the precondition works perfectly fine.
However, if any user is assigned a role besides a Team Member (say Scrum Master), we expect the permissions of Scrum Master to override the Team Member permissions which is not the case. The user is not able to edit even though they have a Scrum Master role because of the Prevent Editing condition for a Team Member.
Is there any option to not allow a user with specific role to edit a particular workitem? (which should be overriden incase of a higher role is assigned).We tried to work around permissions but modify attributes provide the flexibility to user modify a workitem.
Accepted answer
you are mixing two concepts, Permissions and Operational Behavior up which are behaving differently.
Please consider reading https://jazz.net/library/article/292 and https://jazz.net/library/article/291 to better understand how that works.
Permissions are cumulative. Operational behavior work on order of role and first found.
In you example, the Scrum Master should be the Role on the top and you would have to configure the operational behavior for that role and operation, removing the Prevent Editing Operation. from the configuration of the primary role.
Comments
Hello Ralph
Thank you for your reply
In our case, Scrum master role is on the top and there are no preconditions defined for this role. The team member only has "prevent editing" precondition set.
Our concern is if the user has both roles assigned to him, then the precondition for team member i.e. prevent editing dominates. Is there a way to allow a high priority role i.e. Scrum master to dominate preconditions?
If there are no preconditions for work item save, I think you have to check Preconditions and follow-up actions are configured for the Scrum Master Role. That means it is configured, but the operational behavior is actually not configured. Thus it would find it for the highest priority role first, find it empty, and then would not look into additional roles anymore.
The priority role is dominating, however you have to understand how to do that. So I really, really strongly suggest to read the articles in my post above.
Thanks Ralph. The articles were really useful. The solution worked for us.
Hi Amit, please consider to accept the answer then.