Common Team Areas for multiple project areas
I'm using RTC 2.0 and I have a set of users that will be working on multiple project areas. The users are already organized into several teams. There is a hierarchy of teams as well.
Is there away to set up the Team Area Hierarchy once and then share those team areas with all the project areas? I'd like all the project areas to re-use the same teams, rather than recreating the teams in each project area. Right now it looks like one would have to create the same team areas, over and over for each project area and add the same users over and over to each team for each project area. I would think one would also have to be very careful to name the team areas the same way in each project for reporting by team with Insight. Is there a better way? Many thanks, Gaston |
9 answers
I'm using RTC 2.0 and I have a set of users that will be working on multiple project areas. The users are already organized into several teams. There is a hierarchy of teams as well. Currently its not possible to share the team area hierarchy across project areas. Please log an enhancement request stating your requirements. Sridevi, Jazz Process Team |
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 14 '09, 2:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As Sridevi pointed out, one cannot do this in RTC today.
I've submitted work item 99436 "Allow a Team Area to be associated with multiple timelines". The Description states: "I have several customers reporting that they have a team that works on multiple timelines. Currently, they are forced to define separate team area for each of these timelines, and then redundantly make any changes to the membership of the team and the process overrides for that team in each of those team areas. It also makes it difficult to balance the work for members of that team, because one needs to manually adjust the percentage time allocated to these different team areas to reflect the dynamic shift of attention of that user between these different timelines." If you are interested in this functionality, please indicate it by subscribing to the work item (and optionally, adding comments). Cheers, Geoff gastonw wrote: I'm using RTC 2.0 and I have a set of users that will be working on |
Right now I can add Work Items from another Project Area as a Child Link, although it only appears in the Work Item and not in the Plan view.
I'm assuming the answer is No because the Planned For field seems to be specific for a Project Area, but hopefully there is another way. The reason is we had to separate some Work Item Types into separate Project Areas for Access Control reasons, but still want to view them in the same Plan. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 14 '10, 4:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Take a look at work item 101846 (planned for 3.0 M4). It will allow you
to use another project area to determine read-access control of a work item. It sounds like this should handle your use case. Cheers, Geoff miwalker wrote: Right now I can add Work Items from another Project Area as a Child |
Take a look at work item 101846 (planned for 3.0 M4). It will allow you Right now I can add Work Items from another Project Area as a Child Thanks Geoff, It does seem to match what we're looking for. One clarification: When the Enhancement mentions "work item" is that referring to the Type? I see Defect as a Work Item Type where Defect 51 is a Work Item. Maybe I have my definitions incorrect. I would want to be able to restrict read access to a specific Work Item Type and all the records created for that Work Item Type. |
On 1/14/10 9:37 PM, miwalker wrote:
Right now I can add Work Items from another Project Area as a Child Having work items from multiple project areas in one plan is not supported. The reason is that each project area might have a completely different configuration, e.g. the set of attributes a work item has might differ. -- Cheers, Johannes Agile Planning Team |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 15 '10, 9:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You are correct that work item 101846 allows you to control the
read-access project area for a particular work item. What you want to do is effectively to say "any work item of this particular type should be read-access controlled by this specified project area". Please go ahead and submit a work item requesting this enhancement, and mark it as being related to work item 101846. Cheers, Geoff miwalker wrote: gmclemmwrote: Thanks Geoff, It does seem to match what we're looking for. One clarification: When the Enhancement mentions "work item" is that referring to the Type? I see Defect as a Work Item Type where Defect 51 is a Work Item. Maybe I have my definitions incorrect. I would want to be able to restrict read access to a specific Work Item Type and all the records created for that Work Item Type. |
You are correct that work item 101846 allows you to control the I think we can easily fulfill this using the new support for default and dependent attributes. The security context of a work item is an attribute and would depend on the type. I have created https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/103339 -- Regards, Patrick Jazz Work Item Team |
You are correct that work item 101846 allows you to control the I think we can easily fulfill this using the new support for default and dependent attributes. The security context of a work item is an attribute and would depend on the type. I have created https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/103339 -- Regards, Patrick Jazz Work Item Team Thank you Patrick! |
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.