Child pages
  • Migrating RMsis data across JIRA-RMsis installations
Skip to end of metadata
Go to start of metadata

 

 

 

In this presentation we will look at how we can migrate RMsis data to a different JIRA-RMsis instance.

  • RMsis provides a mechanism to migrate a project data across JIRA + RMsis installations, but this requires a series of steps to be followed.

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

    • the ID of entities are regenerated
    • while, the Traceability information still refers to old ID's of entities
  • 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

  1. Prerequisite for importing relationships with JIRA Issues is that 
    1. the JIRA Data should be migrated first
    2. The Issue ID's should not change, when the JIRA Issues are migrated
  2. Export Requirements in CSV format
  3. Export Test Cases in CSV format
  4. Export Traceability in CSV format
  5. Import Requirements from CSV file
    1. Map old ID to Alias field, while importing.
  6. Import Test Cases from CSV file
    1. Map old ID to Alias field, while importing
  7. Import  Test Case relationships from the CSV format 
    1. This step uses the same CSV file as in the previous step, but the import process is different
  8. Import Traceability information using the CSV file.
    1. Select the use of Alias Field, since the ID's would have changed across installations.
    2. Select the option to map JIRA Issues as well, if you wish to reestablish those relationships in the new instance,
  9. In case some checks (like cyclic dependency check) fail, some relationships will not be established. These will be reported in the RMsis log file.
  • No labels