Copy Tracker Views
Since Codebeamer release 2.0, public and private tracker views can be copied from one tracker to others within the same project.
To copy a tracker view,
1. Open the 
, select the relevant private or public tracker view and click the Copy link at the top.
, select the relevant private or public tracker view and click the Copy link at the top.2. In the Copy Tracker View Filter options window,
◦ Select the destination tracker(s)
◦ Change the name of the view to be used in the target tracker(s)
◦ Perform the field mapping if necessary
3. Click Copy to finalize the process.
When copying a view, not only the fields are mapped but all the set filters, logics and options are copied from the saved tracker view.
 | Limitations • The Copy Tracker Views function is not available on the reference selector overlay. • Traceability Views cannot be copied. • In the case of the expert filter, only the cbQL query is copied. Updating the target project and tracker IDs needs to be done by the user. |
Select the Destination Trackers
A tracker view can be copied to one or more target trackers and working sets which can be selected in the Destination Tracker(s) drop-down menu. working sets other than the default working set are displayed indented in the drop-down list to aid the visual division of those trackers form the default ones.
 | The user must have Public View and Item Template - Admin permission for the target trackers as well to be able to copy the relevant view and create it in the target trackers. |
Only those target trackers and working sets can be selected in the drop-down list which the user has permission to.
Name of the Copied Views in the Target Trackers
The names of tracker views are unique within trackers.
The name of tracker views can be modified in the Name of the destination views field. If the original name of the copied tracker view is kept, and that name is already taken in the target tracker, Codebeamer automatically appends an ascending number suffix to the name of the tracker view based on the number of versions already created of the related view. For example, GROUP BY filter 1, GROUP BY filter 2 and so on.
Field Mapping
In the Field Mapping section, filters and options can be mapped to the appropriate fields of the target trackers. If logical filters, for example has Association, are applied in a saved tracker view to be copied, there are no fields to be mapped.
The Field Mapping drop-down menu only lists fields that are of the same type as the original field and the user has access to. working sets, if any, are displayed indented. If the target tracker contains a field with the same name and type as the source field, that field is automatically selected from the list. If such a type of field exists in the target tracker but with a different name, it needs to be selected manually from the drop-down list. Once the mapping is done for the relevant field, a tick icon is displayed on the right of the field name.
In case a field is mapped to the wrong target field, or the Do not include option is selected from the drop-down list for that field, the filter does not work on the target field.
If no mapping option is selected for a field, an x icon is displayed on the right of the field name. Copying a view with unmapped fields is not allowed, and the following warning message is displayed:
| | Please select all mappings. |
All the fields must be mapped, or the Do not include option needs to be selected to be able to copy a view.
After clicking Copy, a message confirms that the copying of the view is executed. For example:
| | 1/1 views were successfully copied to the destination trackers with the name ORDER BY Summary Asc filter 1. |