Setting up a new project area with existing project settings
There are two ways to seed a new project area with the settings from an existing project area. One way is to copy the existing project properties to a new project, and the other way is to use a project area template.
Important: When you copy the saved queries from the source project area to the target
project area, the queries that contain missing references in the target project area are
automatically deleted from the target project area. To avoid automatic deletion of the saved queries
from the target project area, select false from the Delete
imported queries with missing references list in Advanced
Properties.
The following table compares the settings that can be brought over to the new project area by using these two approaches:
Settings | Copy Settings | Template |
---|---|---|
Artifact Constraints | Y | Y |
Artifact Export Preferences | Y | Y |
Artifact Templates | N | Y |
Automated Test Preferences | Y | Y |
Build Provider | Y | N |
Categories | Y | Y |
Configuration Management Preferences | Y | Y |
Custom Attributes | Y | Y |
Execution Preferences | Y | Y |
Execution Record Preferences | Y | Y |
Execution States | Y | Y |
Lab Resource and Channel Properties | N | N |
Link Validity | Y | Y |
List View Queries | Y | N |
Manual Script Preferences | Y | Y |
Project Execution Variables | Y | Y |
Quality Objectives | Y | Y |
Related Sites | Y | Y |
Report Properties | Y | N |
Requirement Risk Preferences | N | Y |
Risk and Risk Profiles | Y | Y |
Saved Queries | N | Y |
Shared Resource Locations | Y | Y |
Table Layout | N | Y |
Test Case/Suite Preferences | Y | Y |
Test Plan Environment Types | N | N |
Test Result Preferences | Y | Y |
Test Script Preferences | Y | Y |