Project (Template) Import/Export restrictions

Restrictions

• Importing projects from templates created with higher codeBeamer versions is not supported.
• Only the head revisions of project artifacts and work/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 will get 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.
• TestRun tracker configurations are exported, but TestRuns are not.
• Baselines are not exported, because they refer to history information.
• Source code related data (repositories, commits, pull-requests, etc.) are not exported.
• Upon import, all imported entities will get new Ids and a revision of 1. The owner/submitter of all imported entities will be user that executed the import and the creation/submit date of all entities will be the date of the import.
• Only Interwiki-Links can be restored properly upon import. Absolute URLs or Wiki Plugin parameters that refer to exported entities will most probably be broken after a re-import.
• Caution: During the export/import, all entities to export/import including comments and attachments are loaded into memory. If there are lots of entities to export/import, or if there are huge attachments, you may need several GB of free memory for an export/import, or the export/import will fail with an OutOfMemoryException.
• Since EMMA 21.09: Project Import does not support applying configurations that were exported in a pre-Emma environment. However it can be bypassed with an Application Configuration projectImport@enableImportingFromNotSupportedCodebeamerVersions.

Reference Handling Restrictions

codeBeamer user can create reference fields in tracker configurations. The type of the reference can be project, tracker, work item, ... . For example: user can create a work item field where trackers can be set in field reference filters. If these references are not in the exported project, user need to know about these if the user would like to import this project. Now user can download this reference list during the import process:

This is a CSV file and it can be downloaded by click to "here" link. It can be open by excel but you should import it because of the UTF-8 encoding.

Cross Reference CSV file

The CSV File contains 3 tables. Example of this file:

Cross Reference table

This table contains the references to other project artifacts.

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

Second table contains work items which has an invalid reference to a missing artifact. So this artifact is not used in the tracker configuration and it is not in the first cross reference table.

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 third table contains fields which has a special computed formula. The formula contains a special function: hasSuspectedLink, hasReferringReview, hasUpstreamSuspectedLink, ... .

Columns:

• filed: the tracker filed where we found the function
• function: the special function