{"id":1642,"date":"2017-05-25T09:59:53","date_gmt":"2017-05-25T08:59:53","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=1642"},"modified":"2017-05-25T09:31:09","modified_gmt":"2017-05-25T08:31:09","slug":"merging-items-together","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/merging-items-together\/","title":{"rendered":"Merging Items Together"},"content":{"rendered":"

Merging Items<\/h2>\n

One or more requirements or system notes can be merged into either a new item or an existing item. Merging items<\/em> combines their frames, concatenating frames that appear in two or more of the source items. Cross references are created between the requirements being merged and the merged result.<\/p>\n

You can control the effect on the item’s key, origin, reference and category codes. The merged item<\/em> can be cross referenced to everything that the sources were, as well as to the sources themselves. The source requirements can be deleted after the merge (if you have read-write access to them) if required.<\/p>\n

When multiple items are merged, conflicts arise when their components differ. Fields in the Item Merge<\/strong> dialog with a blue border show conflicts between the selected items. The Options<\/strong> section in this dialog helps define how such conflicts can be resolved.<\/p>\n

\"Dialog
Item Merge dialog<\/figcaption><\/figure>\n

Click here<\/a> to see the steps on how to merge your requirements\/system notes.<\/p>\n

 <\/p>\n