White Paper on Project Export-Import in TopTeam

TopTeam repository is organized in the form of Projects and sub-Projects. TopTeam allows you to export and import records. However, this export and import feature has its limitations on what all can be imported and which fields will be imported, etc. Using the Import Project feature almost all record information along with its Traceability can be imported.

This is a solution if you want to merge multiple TopTeam repositories into one.

This feature however, should NOT be considered as a:

• Repository Backup
• Repository Synchronizer – This function only imports records and does not synchronize existing records i.e. you cannot import records mutliple times.

• Export Project to File allows you to export data from one or more Projects along with the reference system data into a file (*.prj.ttmdat). The exported file format is a TechnoSolutions proprietary format, which can be used only by TopTeam’s Import Project feature.
• You can import the exported .prj.ttmdat file using Import Project from File option into the same or a different TopTeam repository.

Project

• A new Project is added in TopTeam repository when you perform an import.
• If you are trying to import the same Project again then the artifacts will be imported into an existing Project and a new Project will not be added.
• Project Record Types are imported.

Repository Objects

• All Repository Objects are imported except Review Packages and Test Runs.
• Child tab data for Comments, Attachments and Traceability are imported.
• A new ID is assigned to records that are imported.
• A reused record will be imported as a normal record.

Tracking Items

• All Tracking Items are imported.
• Child tab data for Comments, Attachments and Traceability are imported.
• A new ID is assigned to records that are imported.

Fields

• All fields of Repository Objects and Tracking Items are imported except for the following:

1. Is Suspect – If a link is suspected the object is marked as suspect however, if there is no suspect link and still the object is suspect in the exported project then, it is not a suspect record after the import.
2. Assigned To/Owner – Field is imported if the same name of the user exists in the destination repository, if not then the field is not imported.
3. Created Date, Version Created Date and Time Stamp of the record is the same as it is in the exported project.
4. Created By, Version Created By and Last Updated By of the record is the same as it is in the exported project.

• List type of fields are populated when the same value exists in the destination repository, else it is not imported.
• Custom fields of type Team Members and Project are not imported.
• State type of field will be populated if the same state exists in the destination repository, else it will be populated with the initial state of the Record Type of the record.

1. System Configuration Settings

• Custom Record Types of exported file are not imported, however, you can map them with any other compatible Record Types in destination repository.
• Record Type Traceability Rules are not imported
• Custom fields of exported file are not imported however, you can map them with any other compatible Record Type fields in destination repository.
• Record Type Versioning fields configuration settings are not imported

2. Records in a project which are of following types are not imported:

• Review Packages
• Test Runs
• Custom Diagrams
• Baselines
• Records which are in Recycle Bin
• Data from Checklists tab
• Data of Multi-value type of fields
• Version history of records

3. Project Configuration Settings

• Project Team Members and their security grants
• Project Workflow Rules
• Project Settings – Cascade Suspect settings
• Notification Subscriptions for Team Members

4. Links with records of other projects are not imported
5. Release Deliverables of other projects are not imported
6. OneView

• Package Structures applied to Package sections are not imported
• Layouts of OneView Sections are not imported
• Filters specified in OneView Sections will not work after import if custom/virtual fields were used in the filters. These fields need to be reconfigured after import.

• To import project from file, the schema version of export and import TopTeam Database Schema should be the same.
• Import is not rolled-back if you cancel the operation in the middle of the import.
• Every time you import a Project, you need to specify the Record Type and Field mappings. Mapping that was set up the last time is not recalled.
• Records will not be imported or synchronized if the record exists in the destination repository, even though it is in the Recycle Bin.
• Notifications for any of the imported records will not be set up for any users.
• You need “System Administrator” or “Create Root Project” permissions to import an exported project.

• If there is a new/different record with the same name already existing in the repository at the same location, the import process will still import the record. It will not enforce unique name rule for imported records. As a result, records with same names may be imported.
• If different Requirement Types from export file are mapped to a single Requirement Type in destination repository, then there is a possibility that multiple header Requirements may be created in a Requirements Document even if it is in Strict mode.

How to export and import TopTeam Projects

Revised: June 11th, 2019