Project Import and Export Restrictions

This page provides information on general restrictions for importing projects and reference handling restrictions.

List of General Restrictions

Importing or exporting a project has the following restrictions:

• Importing projects from templates created with higher codebeamer versions is not supported.
• Only the head revisions of project artifacts and work or configuration items are exported, including comments, attachments, permissions, and associations, but without history.
• Project members are exported, but because users and user groups are not part of the project, they can only be re-imported if users and groups with the same names already exist in the target system upon import.
• Tracker configurations are exported completely, but the tracker inheritance information gets lost, if the template tracker is not part of the project to export.
• References (interwiki links in wiki texts, associations, reference fields) to entities outside the current project are exported, but they can only be imported, if entities with the same name at the same location already exist in the target system upon import. However, reused step references are not included in a cross-project import or export. Absolute URLs or wiki plugin parameters that refer to exported entities might get broken after a re-import.
• TestRun tracker configurations are exported, but TestRuns are not.
• Baselines are not exported, because they refer to historical information.
• Source-code related-data (such as repositories, commits, pull-requests) are not exported.
• Upon import, all imported entities will get new ids and a revision of 1. The owner or submitter of all imported entities is the user that executed the import. The creation or submission date of all entities is the date of the import.
• Caution: During the export or import, all entities to exported or imported, including comments and attachments, are loaded into memory. If there are lots of entities, or if the attachments are large, users might need several GB of free memory, or the export or import fails with an OutOfMemoryException.
• Since codebeamer 21.09 (EMMA), project import does not support applying configurations that were exported from versions earlier than codebeamer 21.09. However, it can be bypassed with an application configuration. For more information, see Application Configuration.

Reference Handling Restrictions

codebeamer users can create reference fields in tracker configurations. The type of the reference can be project, tracker, work item. For example, a user can create a work item field where trackers can be set in field reference filters. User can download this reference list during the import process:

This is a CSV file and it can be downloaded by clicking the here link. It can be opened in Microsoft Excel but users should import it because of the UTF-8 encoding.

Cross Reference CSV File

The CSV file contains three tables. Example of this file:

Cross Reference Table

The cross reference table contains the references to other project artifacts. It has the following columns:

• Reference: the reference to another project artifact.
• Type: the reference type (project, tracker, work item).
• Project: project of reference or empty if it is a project.
• Tracker: tracker of reference or empty if it is a tracker.
• Mapped target: the mapped target reference if it is found or unresolved.
• Path: where we found the refence in the tracker configuration.

Item Table

The item table contains work items that have invalid references to missing artifacts. This means that the artifact is not used in the tracker configuration and it is not in the first cross reference table. The item table has the following columns:

• Reference: the reference to another project artifact.
• Type: the reference type (project, tracker, work item).
• Project: project of reference or empty if it is a project.
• Tracker: tracker of reference or empty if it is a tracker.
• Path: the item where we found the invalid reference.

Field Table

The field table contains fields that have a special computed formula. The formula contains a special function, such as hasSuspectedLink, hasReferringReview, hasUpstreamSuspectedLink. The field table has the following columns:

• Field: the tracker filed where the function is found.
• Function: the special function.