Bug 705712

Summary: Make (some) topic relationships bi-directional
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: Web-UIAssignee: Matthew Casperson <mcaspers>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: cbredesen, lcarlon, topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-01 10:36:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joshua Wulf 2011-05-18 08:27:13 UTC 
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?
Comment 1 Matthew Casperson 2011-05-24 02:47:18 UTC 
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.
Comment 2 Joshua Wulf 2011-06-01 10:36:31 UTC 
Verified.

Document: one and two-way relationships - how they are made, and how they are conventionally used (topic to overview, reference to task, etc.)