RTC integration with Siebel, Remedy, etc.
16 answers
There are Bridge connectors for a variety of Rational repositories (e.g.
ClearCase, ClearQuest, Synergy, Change, DOORS). In addition, various
groups are writing bridges using the OSLC API's (see
www.open-services.net for examples).
Cheers,
Geoff
On 10/6/2010 8:37 PM, smithkane88 wrote:
ClearCase, ClearQuest, Synergy, Change, DOORS). In addition, various
groups are writing bridges using the OSLC API's (see
www.open-services.net for examples).
Cheers,
Geoff
On 10/6/2010 8:37 PM, smithkane88 wrote:
Is it an Bridge Connector planned to connect RTC with other systems?
Hello,
I know how to use the work item dependencies, duplicates, etc. within a project. However, I'm wondering if there is an elegant way to track cross project dependencies? E.G. Team 1 constructs component A, Team 3 constructs component C and D. Component D uses a change set from component A, thus, the possibility exists that some defects will be shared between different teams working on different projects. Is there a way to tie one defect to separate projects? I don't see a way to make a work item dependent, or related, to another project, other than creating a new work item for Team 3 in the above example.
Thanks, Mark
I know how to use the work item dependencies, duplicates, etc. within a project. However, I'm wondering if there is an elegant way to track cross project dependencies? E.G. Team 1 constructs component A, Team 3 constructs component C and D. Component D uses a change set from component A, thus, the possibility exists that some defects will be shared between different teams working on different projects. Is there a way to tie one defect to separate projects? I don't see a way to make a work item dependent, or related, to another project, other than creating a new work item for Team 3 in the above example.
Thanks, Mark
Hello,
I know how to use the work item dependencies, duplicates, etc. within a project. However, I'm wondering if there is an elegant way to track cross project dependencies? E.G. Team 1 constructs component A, Team 3 constructs component C and D. Component D uses a change set from component A, thus, the possibility exists that some defects will be shared between different teams working on different projects. Is there a way to tie one defect to separate projects? I don't see a way to make a work item dependent, or related, to another project, other than creating a new work item for Team 3 in the above example.
Thanks, Mark
I know how to use the work item dependencies, duplicates, etc. within a project. However, I'm wondering if there is an elegant way to track cross project dependencies? E.G. Team 1 constructs component A, Team 3 constructs component C and D. Component D uses a change set from component A, thus, the possibility exists that some defects will be shared between different teams working on different projects. Is there a way to tie one defect to separate projects? I don't see a way to make a work item dependent, or related, to another project, other than creating a new work item for Team 3 in the above example.
Thanks, Mark
page 2of 1 pagesof 2 pages