Versions Compared

Key

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

...

  • 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 Key Alias" check box, since the ID's would have changed across installations.
  • Select the projects whose relationships are to be imported.
  • Select the "Map JIRA Artifacts" checkbox as well, if you wish to reestablish those relationships in the new instance


Import Test Run Status Via CSVusing CSV file

When a user decides to import the status through a CSV import; the status of test cases with matching External Ids/Test Case Ids are updated.

  1. Click on the "CSV Import" button. Status can be updated or imported through a CSV file.

2. Now upload a CSV file which contain that contains the status of the entities like Test cases .and click on the Next Step button

3. In this the next step, need to map the source attribute with the target attribute.  Choose either the Id column or External Id column but not both.

Map Id column if this is to be used for mapping the Test Cases in CSV file. This is applicable if the instance remains unchanged.

 

Map External Id column if this is to be used for mapping the Test Cases in CSV file. This is applicable when the source and destination instances are different.

4. Now In the next step, map the status values. Check the default mappings specially TS-Status as RMsis sets it to pass if it's null or blank. Finally, click on the import button.


5. Here in the UI you can see that the status is importedThe status of Test Cases with matching Ids in the CSV file will be updated.


Info
titleNote on errors

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

...