It's all about the answers!

Ask a question

Links between RTC and DNG visible only from RTC after merging DNG streams


Bob 3 (121119) | asked Oct 26 '17, 12:09 a.m.
retagged Dec 28 '17, 1:54 a.m. by Minakshi Jaint (5113)

I am experiencing some strange link behavior when doing cross-tool linking between DNG and RTC and using local DNG streams. When a link is made between DNG and RTC for one branch of a set of DNG streams, and then that branch is later merged back to the main DNG stream, the link to RTC appears to be lost from the DNG side but is maintained from the RTC side. 


Has anyone else encountered this behavior?

I am running CLM 6.0.3. 

One answer



permanent link
Geoffrey Clemm (29.5k23035) | answered Oct 30 '17, 4:50 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

When an RTC work item is linked to a versioned DNG artifact, it is linked to that DNG artifact in a particular global configuration (for the rules about what global configuration it is associated with, see:

So you will always see the link from the work item (pointing to that artifact is the associated global configuration), but you will only see the backlink from that versioned artifact when your current global configuration is exactly that associated global configuration.   

I believe there are some DNG contexts where you are given the choice to see all work items that link to the artifact, not just to the ones linked to your current global configuration context, but we'd need a DNG expert to verify that.




Comments
Bob 3 commented Nov 02 '17, 4:53 p.m. | edited Nov 02 '17, 4:54 p.m.

This brings up a larger question in my mind about DNG and handling links when it comes to delivering/accepting changes from streams and change sets: 

Why aren't links part of the stream/change set merge options? It seems to me that there should be another page of the stream/change set merge wizard that deals with links and whether they should come with the changes to the artifacts or not. 
Through version 6.0.4, links are ignored in the stream/change set merge process and do not come with the artifacts.
 

Can anyone shed some light on this?


Geoffrey Clemm commented Nov 03 '17, 5:32 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

In a versioned artifact, a link is part of one of the two artifacts being linked.  That artifact is called the "source" of the link ... the other artifact is called the "target" of the link.  Any link that is  owned by the artifact being merged is part of the merge process.  In the case of workitem-to-requirement links, the source of the link is always the work item.


One of the reason the system is designed this way is that if both artifacts were treated as owning the link, you are likely to have a large number of conflicts whenever you change to a new baseline of a set of artifacts which don't agree on whether a particular link exists.   Another reason is that you would never be able to create a link to an artifact in a baseline artifact (because an artifact in a baseline cannot be changed).   This would mean that if you had a baseline of requirements in your global stream, you would not be able to create new links (say, with new test cases) with those requirements.   

Your answer


Register or to post your answer.