Other Import Considerations

Consider the following additional behavior during import processing.

Duplicate Inventory

Two inventory items are considered identical between the source and target project if they are associated with the same repository item (by component ID). Duplicate inventory is resolved during the import by overriding all fields in the target project with information from the data file to be imported, with the exception of empty data in the data file.

Manually Unreviewed Files

A codebase file that is manually “unreviewed” in the source project does not retain its unreviewed status in the target project if the target codebase scan has marked the corresponding target file as “reviewed”. This occurs because the data file to be imported stores information about only those codebase files that have been marked as reviewed in the source project. Hence, no information about the unreviewed file exists in the import data to overwrite information for this same file in the target project.

If, during a standard import, you want to retain the reviewed and unreviewed status of codebase files as defined in the source project, manually mark all of the codebase files in the target project as unreviewed before importing the data file.

Open topic with navigation