When requirement link (satisfy or satisfy by) between artifacts of two modules is created, reverse link in the view is not visible from second module if we link Artifacts by entering into folders.
When requirement link (satisfy or satisfy by) between artifacts of two modules is created, reverse link in the view is not visible from second module if we link Artifacts by entering into folders. The reverse link is shown if we link the artifact by entering into target module. But, how does an end user comes to know about this?
Accepted answer
Links are context-sensitive. When you link an artifact in a module to another artifact in another module, that link (and its reverse) can only be seen from those modules. A module-artifact-TO/FROM-module-artifact link will never be seen in the base artifacts, e.g. when viewing the artifacts in their folders.
If you were to make a base-artifact-TO/FROM-base-artifact link, you can see it in modules by pressing the More Actions module menu button (3 horizontal lines in upper right), then choose "Include links, tags, and comments from base artifacts".
I agree with Keith that users have to be educated. Tell them to work only in modules if that's the paradigm you're working in.
One other answer
This is deliberate and is part of the reuse approach in DNG. Links are specific to their location. This allows you to reuse the same requirement in multiple places, but each place only shows links that are relevant to that location. If you are using modules, it is generally good practice to not use the artifacts in the folders directly. I would recommend that users are trained in this approach.
