Requirements Library
To watch a video about the requirements library, click
here.
When you are building a product, you may want to reuse the same requirements in multiple versions. A requirements library is a collection of requirement trackers. When the original issue is changed, you can use the suspected link and Diff features to determine if you must apply the changes to the copied requirement.
You can access the requirements library

on the right panel on the document view of requirements trackers.
Initially, the requirements library lists all non-empty requirements trackers from all projects that you can access. You can customize the list of trackers by clicking

above the tree.
Configuring the Requirements Library
After clicking

, you can select the trackers that you want to see in the requirements library. This is a user setting, so you will see the same list of requirements trackers in every document view.
| Codebeamer stores the list of the selected trackers. Therefore, when you add a new requirements tracker to your project, you must reconfigure the library to display the new tracker. |
Reusing Requirements from the Library
To reuse a requirement from the library, drag the node in the library tree to the tree on the left side or to a requirement in the middle panel.
If there are custom fields in the original issue, they should be mapped automatically. If they are not, you will see a list of the mapping problems and can decide if you still want to copy the requirement.
If the item that you want to copy has verifying test cases, you can select Copy the Test Cases. The test cases of the requirement will be copied to the selected test case tracker, and the copies will be linked to the requirement copy. You may need to define the field mappings.
To create a new copy in your tracker, click Save. The parent of the new requirement is the requirement to which you dragged the original requirement.
Codebeamer creates an association of type copy between the original requirement and the copy. The trigger suspected parameter is set to true for this association. Therefore, when the original issue is changed, the suspected link is triggered on the association.
| Issue properties, comments, and associations are copied to the new requirement. |
The copied nodes are marked with

in the left tree.