RMsis provides a mechanism to migrate a project data across JIRA + RMsis installations, but this requires a series of steps to be followed. There are some key considerations, when migrating as mentioned below.

Use of ID Alias

The primary mechanism available today is to export data as CSV file and import it in another installation in the CSV format.

However, when we migrate data across installations

hence it becomes essential to store a map of the old ID's vs new ID's; so that either can be used, when required. The CSV import process, now provides a mechanism to store old ID's as Alias.

Steps to Migrate Data across JIRA + RMsis Installations

Prerequisite for importing relationships with JIRA Issues is that

Export Requirements in CSV format

Export the requirements in a CSV file by using the "Export to CSV" icon.

Export Test Cases in CSV format

Export the test cases in a CSV file by using the "Export to CSV" icon.

Export Traceability in CSV format

Export the traceability data in a CSV file by using the "Export to CSV" icon.

Import Requirements from CSV file

Click on the "CSV Import" button.

Map old ID to Alias field, while importing.

Map Id with Key Alias in Step 2 of the import process.

Import Test Cases from CSV file

Click on "CSV Import" button and then on "TC Entities" to import test cases.

Map old ID to Alias field, while importing

Map Id with Key Alias in Step 2 of the import process.

Do not map the TS- Id field while importing the CSV file (Remove mapping of TS-Id field while importing the CSV file)

Import Test Case relationships from the CSV format

Import Traceability information using the CSV file.

In case some checks (like cyclic dependency check) fail, some relationships will not be established. These will be reported in the RMsis log file.