Confusion on permissions an hierarchical teams
The article here on permissions (and the article it points to):
http://jazz.net/library/article/291
Lead me to believe that when I have the following:
1. Project 1 with Role Z and default team in Project 1 has all permissions for work items for Role Z, only partial permissions for default role
2. Team A - no process customization override
3. Team A' - child of team A with no process customization override
4. User Lambda - member only of Team A' and is in the "Z" role for that team
I should be able to do all work item operations as user Lambda. Unfortunately this appears to not be the case. Instead I get permissions errors showing that it is run in the context of Project 1 for the default role.
Am I missing something?
I'm on 2.0.0.2 iFix 4 if that makes a difference.
http://jazz.net/library/article/291
Lead me to believe that when I have the following:
1. Project 1 with Role Z and default team in Project 1 has all permissions for work items for Role Z, only partial permissions for default role
2. Team A - no process customization override
3. Team A' - child of team A with no process customization override
4. User Lambda - member only of Team A' and is in the "Z" role for that team
I should be able to do all work item operations as user Lambda. Unfortunately this appears to not be the case. Instead I get permissions errors showing that it is run in the context of Project 1 for the default role.
Am I missing something?
I'm on 2.0.0.2 iFix 4 if that makes a difference.
5 answers
Hi,
I believe the issue here may have to do with your work items configuration. Assigning User Lambda the Role Z in Team A' only gives them permissions for work items which are associated with Team A' and any inheriting team areas.
You would not be able to do all work item operations as User Lambda for work items associated with Team A or Project 1. By default, new work item categories are associated with the project area, so you may need to specifically associate your categories with your team areas. You can do this from the Work Item Categories tab in the project area editor.
Hope this helps,
Parker
I believe the issue here may have to do with your work items configuration. Assigning User Lambda the Role Z in Team A' only gives them permissions for work items which are associated with Team A' and any inheriting team areas.
You would not be able to do all work item operations as User Lambda for work items associated with Team A or Project 1. By default, new work item categories are associated with the project area, so you may need to specifically associate your categories with your team areas. You can do this from the Work Item Categories tab in the project area editor.
Hope this helps,
Parker
I thought I had tried this to make sure it was not the issue. I did it again and you are correct. Does user Lambda's role in A' apply to other permissions outside of work items - and it is only work items that share the additional context of which category the work item is being filed against?