Copying Configurations into Working-Sets
The configurations of any parent Working-Set can be copied into the derived Working-Sets.
 |
PTC recommends you edit the configurations of the Default Working-Set and copy it to all the relevant derived Working-Sets.
|
 |
To copy configurations into Working-Sets, the following permissions are required:
• Working-Set - Admin
• Tracker - Admin
• CMDB - Admin
If any of these permissions are missing, the Copy Configuration function is disabled.
|
To copy the configurations into Working-Sets:
1. On the top right next to the Working-Set selector of the Trackers tab, click the Gear icon > Copy Configuration.
2. In the Copy Working-Set Configuration window, select the Working-Sets into which to copy the configuration of the parent Working-Set.
3. Click Copy to execute.
When performing a configuration copy, all the settings on the Permissions, State Transitions, and Fields tabs are copied into the selected Working-Sets.
The Copy Configuration function can be applied within the whole Working-Set hierarchy.
If a Working-Set has only one child Working-Set, by selecting the child Working-Set into which to copy a configuration, its parent Working-Set is automatically selected to ensure consistency. If more child Working-Sets are available within a parent Working-Set, you can select into which child Working-Sets to copy the configuration.
Clearing the selection of a parent Working-Set removes the selection of the child Working-Sets as well.
Once the Working-Sets are selected and you click Copy, a background job creates the configuration copy.
Because external references are not allowed in Working-Sets, the field configurations and values of the reference fields are updated after the configuration copy is executed.
For example, a reference field in the default Working-Set collects the references from the default User Story. After copying its configuration into the Working-Set 1.2, its reference field gathers references from the Working-Set 1.2 User Story.
|
|
• The copy configuration operation is terminated in the following scenarios:
◦ A field in the target tracker is deleted or modified in a way that creates conflicts.
◦ A choice value created in the target tracker is deleted.
◦ Configuration changes are detected in the target tracker.
The error message contains a list of items in which changes were detected. You can use this information to clean the data and resume the copy configuration operation.
|
Known Limitations
• On the Escalation tab, the Escalation Views are transferred when copying. However, the created rules are not transferred.
• The settings on the General tab are not part of the copied configuration.