Versions Compared

Key

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

...

  • External Artifacts
  • Requirements
  • JIRA Issues
  • Test Cases

Export

From RMsis 1.8.9.3 and later versions,

A user can export the Traceability view, just by clicking on the Image Added icon on the Top RHS of Traceability Table.

If the user wants to export all the columns present in the Traceability Table to the CSV file, the user needs to click on "All Columns" option.

If the user wants to export only the columns currently visible in UI in the Traceability Table to the CSV file, the user needs to click on "Visible Columns" option.

Image Added


In RMsis 1.8.9.2 and previous versions,

A user can export the Traceability view, just by clicking on the icon on the Top RHS of Traceability Table. All the columns present in the Traceability Table will be exported as a CSV file.

...

  • Select a file to import

           

  • Click on Submit.
  • Consequently
    • All the relationships which can be successfully established are created.
    • In case of any failures, the user is prompted and errors are logged in the RMsis log.

When migrating data across installations, the ID's will change. In such a case, please refer to the following section : Exporting to another JIRA + RMsis installation

Info
titleNote
  • While importing Traceability data via CSV import, the "Use Key Alias" option should be used if 

  • you are importing data from one project to another OR 

  • you are importing data from a different RMsis+ JIRA instance.

  • If you are importing data for the same project, then you do not need to enable the "Use Key Alias" option.

...