Versions Compared

Old Version 19

changes.mady.by.user All (Deactivated)

Saved on

compared with

New Version 20

changes.mady.by.user All (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A project with previously existing project key must exist in JIRA.
  2. JIRA project data are already imported into JIRA using single project restore.
    • All the JIRA issues and Releases must have been imported prior to migration.
      • Check reverse traceability and release tabs in RMsis. JIRA related data related to this project should be visible. 
    • Please ensure that no addition or deletion have been performed in JIRA after the data import in JIRA. 
  3. RMsis is already installed and synced with JIRA so that the project exists in RMsis.
    • Open RMsis and select the above mentioned project.
    • This will sync the project with JIRA and import JIRA issues and releases inside RMsis.
  4. RMsis should not contain any pre-existing RMsis data(Requirements,Test Cases etc related to the project being restored) before the data import.
    • Do not insert any data within this project before the migration.
  5. Workflow of source and destination RMsis must be same.
    • This is necessary if advanced workflow is enabled in the source RMsis.
  6. All the users of source instance must be mapped with new users in destination instance.
    • If the users are different in target instance, please map all the users to pre-existing users of target instance.
  7. Data importer will create Global and local Local custom fields in target instance.
    • Please run the migration validator to ensure that same name custom fields have same data typedoes not exist.
    • If it exists, you will have to rename these fields before data restoration.

Migration Validator

This is a java based utility which is used to validate the above mentioned Pre-Requisites. Please follow the steps mentioned below to perform the validation.

...