redirect traceability links in batch
Posted: Wed Sep 07, 2022 12:35 pmHi All,
We have received a new update for our requirements which we stored in a package e.g. "Reqts v2".
Previously, we linked model elements (activity, block, derived requirement) to the requirements stored in a package "Reqts v1".
Redirecting the links from Reqts v1 to Reqts v2 is a tedious manual process.
Is there a way to automate this task as most of requirements remained identical but they have different Ids (because the import) and are in a different namespace.
FYI, Requirements were imported from DOORS NG into Cameo but originally were imported from a Word doc into DOORS NG.
Many thanks in advance,
/jamel
We have received a new update for our requirements which we stored in a package e.g. "Reqts v2".
Previously, we linked model elements (activity, block, derived requirement) to the requirements stored in a package "Reqts v1".
Redirecting the links from Reqts v1 to Reqts v2 is a tedious manual process.
Is there a way to automate this task as most of requirements remained identical but they have different Ids (because the import) and are in a different namespace.
FYI, Requirements were imported from DOORS NG into Cameo but originally were imported from a Word doc into DOORS NG.
Many thanks in advance,
/jamel