Members/Organizations shared across Project Areas
We are in the process of investigating a migration from RTC 2.0.0.2 to RTC 3.0.1. Once the migration is complete, I will be the new RTC Project Administrator. I have used RTC for source control and task management/tracking but am still reading a number of articles on the project administration side.
One concern that has come up is that we have a development organization in one project area with little customization and the related support organization was moved to a separate project area due to the customizations they wanted to different work items and processes, etc. However, they still work closely with development interlocking regularly. The issue they had on 2.0.0.2 is that they wanted to have organization defined that was shared across both project areas. This way they could easily share queries, etc used by the support team with development management that has a stake in support work.
My understanding is that you define the members in each project area. There really is no way to share things across those areas. Is that correct? Or is there anything new in 3.0.1 to help address this?
One concern that has come up is that we have a development organization in one project area with little customization and the related support organization was moved to a separate project area due to the customizations they wanted to different work items and processes, etc. However, they still work closely with development interlocking regularly. The issue they had on 2.0.0.2 is that they wanted to have organization defined that was shared across both project areas. This way they could easily share queries, etc used by the support team with development management that has a stake in support work.
My understanding is that you define the members in each project area. There really is no way to share things across those areas. Is that correct? Or is there anything new in 3.0.1 to help address this?
2 answers
Depends on what you want to "share". You can link work items across
project areas, and you two project areas can share the same components.
But a query cannot (yet) span multiple project areas, and a plan
cannot span multiple project areas.
Cheers,
Geoff
On 7/26/2011 10:08 PM, piperp wrote:
project areas, and you two project areas can share the same components.
But a query cannot (yet) span multiple project areas, and a plan
cannot span multiple project areas.
Cheers,
Geoff
On 7/26/2011 10:08 PM, piperp wrote:
We are in the process of investigating a migration from RTC 2.0.0.2 to
RTC 3.0.1. Once the migration is complete, I will be the new RTC
Project Administrator. I have used RTC for source control and task
management/tracking but am still reading a number of articles on the
project administration side.
One concern that has come up is that we have a development
organization in one project area with little customization and the
related support organization was moved to a separate project area due
to the customizations they wanted to different work items and
processes, etc. However, they still work closely with development
interlocking regularly. The issue they had on 2.0.0.2 is that they
wanted to have organization defined that was shared across both
project areas. This way they could easily share queries, etc used by
the support team with development management that has a stake in
support work.
My understanding is that you define the members in each project area.
There really is no way to share things across those areas. Is that
correct? Or is there anything new in 3.0.1 to help address this?
Depends on what you want to "share". You can link work items across
project areas, and you two project areas can share the same components.
But a query cannot (yet) span multiple project areas, and a plan
cannot span multiple project areas.
Cheers,
Geoff
On 7/26/2011 10:08 PM, piperp wrote:
We are in the process of investigating a migration from RTC 2.0.0.2 to
RTC 3.0.1. Once the migration is complete, I will be the new RTC
Project Administrator. I have used RTC for source control and task
management/tracking but am still reading a number of articles on the
project administration side.
One concern that has come up is that we have a development
organization in one project area with little customization and the
related support organization was moved to a separate project area due
to the customizations they wanted to different work items and
processes, etc. However, they still work closely with development
interlocking regularly. The issue they had on 2.0.0.2 is that they
wanted to have organization defined that was shared across both
project areas. This way they could easily share queries, etc used by
the support team with development management that has a stake in
support work.
My understanding is that you define the members in each project area.
There really is no way to share things across those areas. Is that
correct? Or is there anything new in 3.0.1 to help address this?
Thanks Geof for the response. I am actually asking the person who asked this question of me for more detail so I can get some clarity on exactly what they want to "share".