Hide Forgot
Relating a topic to a topic overview should make the relationship bi-directional. However, we need to examine whether relating peer topics together is bi-directional. For example: If we use "Deploy an application server to App Server in JBDS 5" effectively a "function" that we call whenever we need it, using either a Rocbook injection, or just a straight up "Related Tasks" injection, then we will end up with a million related tasks on the "Deply an application..." task. Which is not what we really need. Because Topic Overviews are rarer, and wider in their scope, bi-directional links between them and the topics that they encapsulate are smaller in number, and more significant. Can we make it that relationships between [Concept|Task|Reference] topics and Topic Overviews are bi-directional, and relationships between peer topics are unidirectional?
Fixed in 20110524-1227 Added the ability to create 2 way relationships, and swap between 1 way and 2 way relationships easily in the UI.
Verified. Document: one and two-way relationships - how they are made, and how they are conventionally used (topic to overview, reference to task, etc.)