CLM 6.0.2: Suspect Traceability and Configuration Management
Hi,
I have two questions:
1. I am reading this documentation: https://www.ibm.com/support/knowledgecenter/en/SSYMRC_6.0.2/com.ibm.rational.test.qm.doc/topics/c_suspecttrace_tcs.html?cp=SSR27Q_6.0.2
and it has this Note: Suspect traceability is not currently supported in projects that have configuration management enabled.
Is this true? So we cannot get the suspect traceability, the requirements reconciliation features if we enable configuration management?
2. If the note above is indeed true then......if I enable configuration management for one project and not for another will the suspect traceability work for the one that I do not enable the configuration management for?
I have two questions:
1. I am reading this documentation: https://www.ibm.com/support/knowledgecenter/en/SSYMRC_6.0.2/com.ibm.rational.test.qm.doc/topics/c_suspecttrace_tcs.html?cp=SSR27Q_6.0.2
and it has this Note: Suspect traceability is not currently supported in projects that have configuration management enabled.
Is this true? So we cannot get the suspect traceability, the requirements reconciliation features if we enable configuration management?
2. If the note above is indeed true then......if I enable configuration management for one project and not for another will the suspect traceability work for the one that I do not enable the configuration management for?
One answer
Hi Neeta,
In the world of configuration management there is something else for suspect links. Link Validity - this is a much more powerful mechanism which finds validity across the versions.
Please see here and then let me know if this answers your questions:: https://www.ibm.com/support/knowledgecenter/en/SSYMRC_6.0.2/com.ibm.jazz.vvc.doc/topics/c_linkval.html
However, for your 2nd point, once you enable a QM or RM project, then you need to enable any corresponding projects due to the links needing to be handled through the link discovery LDX application and not the old way.
Thanks,
Paul