Yes, Risk items and their risk matrix values can be imported to Ketryx via Jira's External Systems Importer. The instructions below outline the steps needed for this migration. 

WARNING: This migration may potentially cause Risk items in a Closed state to reopen. It is advised to follow this migration path for Risks if there are no risks present in your current Jira/ Ketryx Projects or if maintaining Closed states for Risk items is not relevant to you. 

1. Follow the instructions in our documentation (docs.ketryx.com) to connect a Jira project to a Ketryx project. 
2. Follow the instructions in our documentation (docs.ketryx.com) for Risk configuration and set up your desired risk matrices. 
3. Navigate to the Screens setting of Jira (Top-right gear icon --> Work items --> Screens) and create a copy of the Ketryx Risk screen
4. Add the following fields to the Risk work item screen.
5. Navigate to the Screen schemes setting and find the Ketryx Risk screen scheme and create a copy of it. In the copy of the Ketryx Risk screen scheme, add the copy of the Risk screen you edited in step 4 as the Default. 
6. Navigate to the Work type screen schemes setting and find the Ketryx issue type screen scheme and create a copy of it. In the copy of the Ketryx issue type screen scheme, add the copy of the Ketryx Risk screen scheme you edited in step 5 as to the Risk work type.
7. Navigate to the Project in Jira and create an Epic Work item and name it "Example Epic, to be deleted after the migration".
8. Navigate to the Screens section of the Project settings (Project Settings --> Work items --> Screens) and select the copy of the Ketryx issue type screen scheme you edited in step 6.
9. Go to the Ketryx Project that this Jira Project is connected to. Navigate to the Project Advanced settings and edit the Jira field mapping setting to the following: 

   1. {
      "Initial likelihood of occurrence (P1)": "initialOccurrenceProbabilityText",
      "Initial likelihood of harm (P2)": "initialHarmProbabilityText",
      "Initial severity": "initialSeverityText",
      "Initial risk evaluation": "initialRiskEvaluation",
      "Residual likelihood of occurrence (P1)": "residualOccurrenceProbabilityText",
      "Residual likelihood of harm (P2)": "residualHarmProbabilityText",
      "Residual severity": "residualSeverityText",
      "Residual risk evaluation": "residualRiskEvaluation"
      }

10. Utilize the Jira REST API to identify the identifier number for each Jira Field option. 
    1. "Initial likelihood of occurrence (P1)" = initialOccurrenceProbability
    2. "Initial likelihood of harm (P2)" = initialHarmProbability
    3. "Initial severity" = initialSeverity
    4. "Initial risk evaluation" = initialRiskEvaluation
    5. "Residual likelihood of occurrence (P1)" = residualOccurrenceProbability
    6. "Residual likelihood of harm (P2)" = residualHarmProbability
    7. "Residual severity" = residualSeverity
    8. "Residual risk evaluation" = residualRiskEvaluation
11. In the CSV file used for the Jira External Systems Importer, associate the identifier number with the field option.
12. Upload the CSV file with your risks to Jira using the External Systems Importer. 
13. After the upload is complete and successful, edit the copied Risk screens, Risk screen schemes, and Issue Type Risk Schemes to exclude the added risk fields from step 4. Then, clear the Jira field mapping setting from step 9. It is important to remove these fields and clear field mappings as edits made to Risks in Ketryx will not update the Jira ticket if these fields remain in Jira.

For more information on how to generate Ketryx Select Field option keys, such as "Initial Severity", click here.