Full Project Configuration Deployment
The full project configuration deployment process imports and exports the selected project and its tracker configurations together with all the dependencies from other projects.
The following example illustrates the Project Configuration Deployment feature on two projects:
• Corporate Project: An independent project. This project is made available as a template project to create other new projects. For more information on how to create new projects, refer to Creating a New Project.
• Domain Specific Project: A project created by using Corporate Project as a template. For more information on how to create projects using a template project, refer to Creating Projects by Using Template Projects.
Prerequisites
Refer to the Prerequisites section on the main Project Configuration Deployment page.
Step by Step Procedure
1. As a system administrator, ensure that the application configuration has the following:
"deployment": {
"enabled": true
}
"enabled": true
}
2. Prepare for deployment:
a. In the project to export, click > .
b. Click Export for Deployment.
c. Click on the link to the Deployment Export page that appears on the lower-right corner of the page.
d. For a full deployment, deploy all projects with their configurations. You can also deploy all configuration items by selecting INCLUDE ALL CONFIGURATION ITEMS.
e. Click Export.
3. Download the exported ZIP file.
4. On the target Codebeamer instance, click Apply Project Deployment.
5. At the right side of the Deployment File field, click Attach a file and upload the deployment archive.
6. Wait for the Project import finished message. Click the Project Browser page to visit the deployed project.
Notes and Observations
• The project wiki pages and widgets are not deployed.
• The files from the Documents tab of the source project are not deployed.
• The selected trackers are deployed, however, work items are not deployed.
 | You can deploy the items of all the trackers belonging to the Config Items group if you select them during the export phase on the source environment. |
• Tracker configurations such as state transitions, permissions, fields are deployed.
• If you selected the Import tracker inheritance option when applying the deployment, the deployment process retains the inheritance between the deployed projects on the target environment, as in the following image:
◦ You can enable this option by setting "trackerHierarchyDeploymentEnabled" : true in Application Configuration. For more information refer to Deployment Configuration Options.
◦ The inheritance is retained also in scenarios where you deploy template projects and the target instance has trackers that are already inheriting from the templates that you deploy.
• Project categories are deployed.
• Reports are deployed.
• Project baselines are not deployed.
• Project roles and project members are deployed.
◦ For more information on how project roles and members are handled during the deployment, refer to Project Configuration Deployment - Technical Details.
• Contents of the Trash tab are not deployed.
• Only the default working set is deployed.
• Hidden trackers are deployed.