Why don't permissions show up checked in the Web UI?
I have a team area that grants permission to a role to Save Work Item. In the Eclipse editor for the team area, the Save Work Item permission for the role is checked in the Team Configuration and also in the iterations. In the web editor for the team area, the Save Work Item permission for the role is checked in the Team Configuration but not in the iterations.
Users with the role are able to save work items.
What is going on?
Users with the role are able to save work items.
What is going on?
Accepted answer
This is working as designed.
There is a difference between the way the Eclipse editor and the web UI show permissions. The Eclipse editor shows the permissions that are configured at a higher level within the team area. For instance, if a permission is allowed in the Team Configuration, it shows up as checked in any iterations for the team area. The web UI does not show permissions that are configured at a higher level; it shows only whether or not the permission is configured for the element selected (ie the specific iteration, iteration type, etc).
This is merely a difference in the presentation; the actual permissions are the same and are enforced correctly, as your customer has noted.
Is it necessary to show inherited permissions in the permissions web ui permissions tree? (67734) tracks the discussion about how permissions should be shown in the web and contains a good explanation of how the Eclipse client determines what to show as checked.
There is a difference between the way the Eclipse editor and the web UI show permissions. The Eclipse editor shows the permissions that are configured at a higher level within the team area. For instance, if a permission is allowed in the Team Configuration, it shows up as checked in any iterations for the team area. The web UI does not show permissions that are configured at a higher level; it shows only whether or not the permission is configured for the element selected (ie the specific iteration, iteration type, etc).
This is merely a difference in the presentation; the actual permissions are the same and are enforced correctly, as your customer has noted.
Is it necessary to show inherited permissions in the permissions web ui permissions tree? (67734) tracks the discussion about how permissions should be shown in the web and contains a good explanation of how the Eclipse client determines what to show as checked.