Select Project Baseline and Contents to Export
In Codebeamer 21.04 and older, only the current project data (Head Revision) can be exported.
Since Codebeamer 21.09, the project baseline can be selected for export:
There is also the special Tracker specific baseline setting, that allows to choose individual baselines for each tracker to export:
Codebeamer only allows the export of
• Trackers, that exist in the selected project baseline
◦ Fields, that exist in the selected tracker or project baseline
Select project contents to export
Only export data that the intended Destination system should see and can handle.
Select the tracker to export:
For each selected tracker, the user can restrict the export to items in a specific meta status or to items in a specific tracker view:
If none of the pre-defined meta status filters or tracker views is applicable, a new filter view can be created via New View from the drop-down list.
In case all tracker items are exported (Any status), the full tracker item hierarchy is exported.
When exporting only a sub-set of items, For example, only accepted requirements, parent items (e.g. Folders) might not be exported which result in the requirement to be exported as top-level item.
To preserve the (folder) hierarchy upon export, check Preserve hierarchy (since Codebeamer 9.5 and newer):
Preserve hierarchy also exports all ancestors of the tracker items to export, even if they do not match the selected filter.
The user also needs to select, which attributes/fields of the selected tracker items should be exported:
Codebeamer proposes a default set of fields based on the tracker type, however, more fields can be added, or the selected fields removed.
There is also the option to select all or remove all fields via the appropriate actions in the fields header.
If an embedded table field is selected for export, it also needs to be selected which of the table's columns should be exported.
If Codebeamer should also export information about tracker items, that have been removed, then the field Deleted must be selected. This will include removed tracker items in the export, that will have their ReqIF.ForeignDeleted attribute set to true.
By default, Codebeamer will not export tracker items, that have been removed.
Multiple trackers can be selected for export.
To export items from one tracker including related/referring items from another tracker. For example,
• Customer requirements plus the derived system requirements
• System requirements plus the verifying test cases
then use the References selector:
This way, Codebeamer makes sure, that also the relations between the related/referring items are properly exported:
Additionally, the user can choose to export specific associations of the selected items. For example, the dependencies of the Test Cases:
Only associations to other tracker items can be exported, and only, if the target tracker items of the same association type are also in that export.
Information about associations, that have been deleted, will only be exported, if Deleted is selected under Fields.
This will include removed associations in the export, that will have their ReqIF.ForeignDeleted attribute set to true.
Since Codebeamer 21.09 and newer, trackers to export can be collapsed:
To expand/collapse all trackers at once, right click anywhere in the Trackers column and choose Expand all or Collapse all from the context menu.
