Unable to get this working in RTC 3.0 but work in RTC 2.x
Hi All,
I wanted to verify if this is a defect or not, has logic changed in RTC 3.0. If I wish to allow only Team A to create WorkItem, I perform the following steps: A. Open the Project Area, in the Process Configuration tab, Go to Team Configuration, de-select the option, to "create a WorkItem" under "Save Work Item (server). B. Open Team A from the Team Organization view, in the Process Customization tab, click on Permissions, for the role=Dev, I added the option to "Create a WorkItem" for this role. C. Confirmed Iterations permissions are unconfigured. D. Login via a user only having this Dev role, I still unable to create work item, getting permission denied with the error below. "You don't have permission to Save Work Item ." If I open Team Area Configuration and added the Dev role to Create WorkItem, it works fine. Note: I try this in RTC 2.0.0.2, it works fine for Step A to D. It does not work for RTC 3.0. If anyone has time to try this and suggest what I should check to get this working, would be great. Thanks |
3 answers
I setup the following structure in RTC 3.0 in a project area based on
the Simple Process Template: Project Area: Members: Freddy (Role: Team Member) Markus (Role: Dev) Team Area: TeamA Members: bill (Role: Dev) Team Area: TeamB Members: jason (Role: Dev) The "Save Work Items Permissions" are as follows: Project Area: Enabled for "Team Member", Disabled for "Dev" TeamA : Enabled for "Team Member", Enabled for "Dev" TeamB : Enabled for "Team Member", Disabled for Dev Given the above setup here are the results of logging in as Freddy, markus,bill, jason and attempting to submit a defect: Freddy(Team Member, Project Area): can submit Markus(Dev, Project Area): Permission Denied Bill(Dev, Team A): can submit jason(Dev, TeamB): permission denied So from the above I think it is working as expected. Note also that each user is a member of *either* the project area *or* a team area, not both. Even if I make Markus a member of TeamA, with the Dev role, Makrus still canoont save work items. So I'd check your project/team area memberships. HTH On 13/12/2010 7:23 PM, awong wrote: Hi All, |
I think you should associate a work item category to the team area. The members of this team area with Dev role will have the permission to save a work item only for the associated work item category. You should see "Field Against" in the work item editor. You can only choose the work item category for the team area.
I don't think there is any change for basic permission checking between 2.0.2 and 3.0. There is doc about how to check the permission you might be interested in: http://jazz.net/library/article/32 |
Yes the category is one critical config for the permission. The freshman as me should pay attention to it.
I think you should associate a work item category to the team area. The members of this team area with Dev role will have the permission to save a work item only for the associated work item category. You should see "Field Against" in the work item editor. You can only choose the work item category for the team area. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.