Concept
|
Support Level for Export
|
Limitations / Additional Information
|
---|---|---|
Configuration items type tracker
|
Supported
|
|
Release type tracker
|
Supported
|
|
Component type tracker
|
Supported
|
|
Platform type tracker
|
Supported
|
|
Contact type tracker
|
Supported
|
|
Test set type tracker
|
Supported
|
|
Test configuration type tracker
|
Supported
|
|
Team type tracker
|
Supported
|
|
Area type tracker
|
Supported
|
|
Tracker items from configuration trackers
|
Supported
|
|
Items of other tracker types, including Work item trackers
|
Not supported
|
|
Tracker items from a document type tracker
|
Not supported
|
|
Dashboards
|
Not supported
|
|
Wiki pages
|
Not supported
|
|
Documents from the Documents tab of a project
|
Not supported
|
|
Users and settings for specific users
|
Not supported
|
|
Dependencies not related to the exported project by using reference filters. The dependencies concept includes also the ancestors of the trackers in the inheritance tree, such as parent templates or grandparent templates.
|
Not supported
|
The reference finder only works through reference filters. Other dependencies are excluded.
|
Closed projects
|
Not supported
|
Closed projects are not supported.
• To check if a project closed, open it, click > > Expand the Project Meta Description section.
• Closed projects do not appear for selection on the deployment dashboard page.
• To include a closed project in the deployment, you must reopen it. For more information, refer to Closing/Reopening Projects.
|
Working set configurations
|
Not supported
|
Exporting a project with a working set ignores the working set configurations.
|
Updates of working set configurations during a deployment
|
Not supported
|
Updating an existing project with a working set configuration is not supported during a deployment.
|
Concept
|
Support Level for Apply Configuration
|
Limitations / Additional Information
|
---|---|---|
• Notifications
• Associations
• Attachments
• Configuration icons
• Project calendars
|
Partially supported
|
Exported but not applied on the target system.
|
Computed formulas updates
|
Partially supported
|
ID references in computed formulas are not resolved and updated in computed fields.
|
cbQL updates
|
Partially supported
|
• The name of an entity can be used in cbQL as a reference. These names are not resolved during the import.
• Entities with numeric names (for example, 123 as a project name) are either resolved incorrectly or they break the import.
• Custom field references are not replaced during the deployment.
|
Tracker inheritance
|
Partially supported
|
• Set "trackerHierarchyDeploymentEnabled": true to import the tracker inheritance. For details about this application configuration, refer to the "deployment" section.
• Due to technical limitations, tracker inheritance can slightly change tracker configurations when applied.
• Deploying a template automatically propagates the configuration changes to the trackers that are derived from the deployed template in the target server. The automatic propagation of the configuration changes does not include the configuration parts that are modified in the target server.
• If there are trackers in the trash that have a currently deployed tracker as a template, the template inheritance connection between the template and the trackers in the trash is removed.
|
Project Categories
|
Partially supported
|
• All project categories are moved between the source and the target system.
• Project Category Hierarchies are not applied to the target system. All categories are merged to the root level.
|
Document type trackers
|
Partially supported
|
Items from document type trackers are not exported.
If the deployment of document type trackers is enabled by the "deployment": {"enableDocumentTrackers": true} application configuration, these trackers are shown in the tracker outline of the project after an import.
If the deployment of the document type trackers is disabled by the "deployment": {"enableDocumentTrackers": false} application configuration, these trackers are not shown in the tracker outline of the project after an import.
|
Deletion of tracker configurations on the target environment
|
Partially supported
|
For details about the deletion of the tracker configurations on the target environment, see Project Configuration Deployment - Technical Details.
|
Deletion of tracker configurations on the source environment
|
Not supported
|
|
Broken project category references
|
Not supported
|
|
MxGraphs
|
Not supported
|
|
Broken user references
|
Not supported
|