NOTICE: Our Community is moving. Get more information.
Why does the copy / paste requirement option paste a different requirement than what was copied?
This symptom is seen when requirements are being copied/pasted between two different CaliberRM client instances connected to two different CaliberRM Servers.
The copy operation records the ID"s of the requirements to be pasted...When the paste operation is performed the CaliberRM Server looks at the *source ID and then copies requirement data to the *target requirement(s). If the target requirement is in client that is connected to a different CaliberRM Server, the ID of the "copied" requirement is used when creating the new requirement, but the information copied is from that corresponding ID on that server, not from the intended source server.
In cases, the source ID for the copy selection may not exist, in which case an error will be thrown.
The copy/paste operation should only be performed within the same CaliberRM Server. This can be done within the same client, or two clients as long as both are pointing to the CaliberRM Server.
If you must move data between two CaliberRM Servers, you may investigate using the CaliberRM Export and CaliberRM Import Utilities for whole projects which has the same resulting data as from a copy/paste operation. This will include the requirement name, description, details, traces, and UDA fields, though Requirement history and Discussions will not be retained...
More information on using the IMPORT/EXPORT utility on the caliber server can be found in the supplied documentation.
For more isolated or smaller groups of requirements, a DocFactory report may be performed on the source instance and then use the Import from Word feature on the target system. This will only bring over the Requirement Name and Description, and no other attribute information.