...
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.
Import Test Case relationships from the CSV format
- This step uses the same CSV file as in the previous step, but the import process is different.
- Click on "CSV Import" button and then click on "TC Relations".
- Select the "Use Key Alias" check box, since the ID's would have changed across installations.
- Select the "Map JIRA Artifacts" checkbox as well, if you wish to reestablish those relationships in the new instance
Import Traceability information using the CSV file.
- Click on the "CSV Import" button in the Traceability view.
- Select the CSV file from which traceability data is to be imported.
- Select the
use of Alias Field- "Use Key Alias" check box, since the ID's would have changed across installations.
- Select the
option to map JIRA Issues - projects whose relationships are to be imported. (applicable from RMsis 1.8.3 onwards)
- Select the "Map JIRA Artifacts" checkbox as well, if you wish to reestablish those relationships in the new instance
,
Info | ||
---|---|---|
| ||
In case some checks (like cyclic dependency check) fail, some relationships will not be established. These will be reported in the RMsis log file. |