issue related to RQM link in RTC with configuration enabled
Hi Someone who may concern,
We are working on CLM 6.0.4.
Our RQM is GC configuration enabled. We have 2 GC stream for RQM, say GC_1 and GC_2
GC_1 includes local RQM stream which is a initial stream.
GC_2 includes local RQM stream which is a stream created base on initial stream, branched off for several months. So RQM content for GC_1 and GC_2 is different,
Our RTC used FoundIn to do mapping for GC stream, some work items are configured to connect to GC_1 and some others connect to GC_2
So, in RQM context, if we are in GC_1 stream, when we tried to link to RTC work item, we can see RTC work items in GC_1 by default.if we are in GC_2 stream, we can see RTC work items in GC_2 by default. It can work properly.
However, we found for a RTC work item with FoundIn for GC_2, when we tried to create link RQM artifacts in RTC context, we can only find RQM artifacts in GC_1, i.e. the one with the initial local RQM stream. We can not see artifacts under GC_2. And we did not find any place to switch stream in prompt window.
i.e. In RTC context, the link from RTC to RQM for GC_2 is unfeasible.
We have to go to RQM, in RQM context of GC_2, add link to RTC, i.e. creating link in the other direction.
However, our development team consider it as a pain, they want to link them in RTC context.
We are not sure whether it is feasible? how can we select GC_2 in RTC context?
Thanks!
Best Regards,
Jane Zhou
One answer
The most common cause for this situation is that for the particular link type, the work item is actually associated with a different global configuration than expected (or possibly no global configuration). To determine if this is the case, create a link of that type (to whatever artifact is visible in the "create link" dialog). Then navigate that link, and see what the configuration context is in the web view. That is the (global) configuration that should be used by the system when selecting a target artifact, and if that configuration is not the one being used by the link target picker, please submit a defect.
Also, not that you can configure which link types use Found-In, and which link types use Planned-For, and by default, only the "Related-Xxx" RQM links used Found-In ... the others use Planned-For. So make sure that when you are using the above test, which link type you select can affect which global configuration the target picker uses.