why my link to RTC disappear in RM with Global Configuration enabled?
![]()
jane zhou (86●3●30)
| asked Jul 12 '17, 11:15 a.m.
retagged Jan 16 '18, 12:59 a.m. by Minakshi Jaint (511●3) Hi Some one who may concern,
I am working on CLM 6.0.3.
I created a GC stream to contain stream from RM and RQM .
And I add a link in one artifact in RM to a Defect in RTC, with the same GC by modifying Plan for field. I can see this defect by marking "Show only Work Items related to the current Global Configuration".
Then I can see the link show both in RM and RTC, i.e. in RM, When I select this artifact, I can see the link to defect, in RTC, when I select this defect, I can see the link to the artifact.
However, after 10 minutes, when I check again, I found the link in RTC to RM is still there, but the link in RM to RTC disappears. I have double checked, I am in the same Global Configuration Stream. And when I click the link in RTC, I can access the artifact in RM properly.
I am wondering why the link to RTC disappears in RM ?
Thanks!
Best Regards,
Jane Zhou
|
Accepted answer
![]() Hi Jane,
jane zhou selected this answer as the correct answer
Comments Hi Kathryn,
Thanks for your detailed explanation!
We have configured RTC for the release: configure all items at Configuration Management - OSLC Link/Attribute Mapping to point to "Derived from plan for". Create Release by connecting timeline with related GC stream.
So, we are afraid the issue is related to LDX, i.e. it can not update properly. Because we can see link some time,then it disappear... We have asked IT admin for help because we have no permission to check it. Hope it can resolve the issue.
Thanks again!
Best Regards,
Jane Zhou
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, if after you have turned on configuration management in DNG, and set of the appropriate iteration/release/GC information in RTC, and then in the DNG artifact links tab you can see the linked RTC work item, if subsequently that link disappears without you have modifying any of the RTC iteration/release/GC information, or the planned-for attribute of that work item, then that is a bug, and working with IBM support is the right approach. |
2 other answers
![]() Hi, Jane
|