Import

Import risks by adding risk assessments to existing Jira issues, or create new Jira issues directly from Excel or CSV risk registers, including their associated risk assessments.

Import existing Jira issues
Import from Excel or CSV (new Jira issues will be created)
1. Jira Bulk Import
2. or Risk Register Import

1. Import existing Jira issues

Select issues to import with JQL
Select the risk issue fields (optionally)

Clarifications: If no risk fields are selected, the risk assessment will be set to Undefined. The risk model used is either the default risk model or the risk model assigned to the Jira project. Valid inputs include the Risk Matrix impact/probability labels (e.g., Minor/Probable) or the corresponding value array index starting from 1.

2. Import from Excel or CSV

For complex Excel and CSV risk registers we recommend 2.a Jira Bulk Import

2.a Jira Bulk Import

First create Jira issues with Jira bulk import (see picture). Then do the “Import existing Jira issues“

2.b Risk Register Import

Excel columns must be mapped to one of the four types listed below. For 'Risk Columns' and 'Jira Columns,' ensure that the column headers exactly match the names in the tables below. The sheet cannot have empty leading rows or columns, so data should start at cell (0,0).

Example - download example excel

Risk Columns
Jira Columns
Jira Custom Field Columns → info: cannot be mandatory in selected project issue screen. risks are created and populated in two steps
User Columns

Risk Columns (risk severity is then calculated)	Comments

Risk Columns (risk severity is then calculated)	Comments
`inherent probability`	default risk matrix value or index e.g. Probable or 1 with empty cell undefined
`inherent impact`	default risk matrix value or index e.g. Minor or 3 with empty cell undefined
`residual probability`	default risk matrix value or index e.g. Probable or 1 with empty cell undefined
`residual impact`	default risk matrix value or index e.g. Minor or 3 with empty cell undefined

Jira Columns	Comments

Jira Columns	Comments
`summary`
`description`
`priority`
`status`	Only statuses that can be reached from the initial 'Created' status according to the workflow are allowed. This is a API limitation in Jira.
`due date`
`labels`	comma (,) seperated
`created`	Jira automatically created value
`updated`	Jira automatically created value
`resolved`	Jira automatically created value

Jira Custom Field Columns	Comments

Jira Custom Field Columns	Comments
Text Field (single line) or Short text	Excel header shall match existing custom field name
Number field or Number	Excel header shall match existing custom field name
Select List (single choice)	Excel header shall match existing custom field name (Jira company-managed projects)

User Columns

User Columns
If a risk register is created as part of the import. Then all columns not matching above will be created as user columns in the risk register.