cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

treat document versions like branches in case of trace propagation

treat document versions like branches in case of trace propagation

Scenario:

- we have a Lib of "reference" documents (req and test) that have traces. These documents are Versioned (major and minor)

- a new project branches its live-documents (req and test) from a set of  defined versioned reference documents, as a "kickstart". The "validated by" relationship is not copied, but must be propagated into the newly branches live-documents

 

reference live-Doc (in library project) "General System Security Req."

|__ reference versioned-Doc (e.g. 1.0) "General System Security Req. V1.0" 

    |__ branched Live Doc (in development project) "Product XXX System Security Req." 

 

Same for Testsuites.

 

Problem:

currently the versioned documents cannot be use as "source" in the propagate traces tool.

Only the original live-document can be selected as "source" in the propagate traces tool, but the propagate won't do anything, as the "Version" is not a "Branch" (although it technically is) and so the target and source documents cannot be brought in relation.

 

It seems like a Version "breaks the family tree" in terms of trace propagation.

 

 

 

 

2 Comments
Aquamarine
Status changed to: No Plans to Implement
 
Alexandrite

Can you give any explanation why this is not implemented (or working as expected).

 

For our company this behavior is a showstopper when it comes to document versioning.