...
If an issue has a risk assessment attached to it, no matter what its issue type, that issue will appear in the risk registers based on those projects or filters, subject to the settings of those risk registers.
If the issue is of the primary risk type, then it always has a risk assessment attached to it. In the example above, issues of type Story will always appear in a risk register.
New issues that have are of one of the supplementary risk types don’t have risk assessments attached to them by default, but you are able to add risk assessments to them. You can define the supplementary risk types by inclusion or exclusion using the Only and All except options. In the example above, you will be able to add a risk assessment to issues of type Task will appear in the risk register if someone has added a risk assessment to them.
If an issue is neither of the primary risk type nor one of the supplementary risk types, then it’s not possible to add a new risk assessment to it.
If an issue was once a primary risk type, or if it was once a supplementary risk type and the user added a risk assessment to it, then it will continue to appear in relevant risk registers even if the project/app settings are changed to so that it no longer is of the primary risk type or nor a supplementary risk type.
- The primary risk type and supplementary risk types defined here represent defaults. Particular projects can override these defaults.
Risk treatment
This dropdown allows you to nominate an issue link type that defines how treatments are connected to risks. When this relationship is defined, treatments will appear beneath risks on the risk register page (see Viewing Risk Registers and Matrices). If you leave the field blank, then treatments will not appear on the risk register page.
Users typically use this feature to record the treatment plans they have defined for their risks. Recording treatment plans in separate issues will enable you to quickly reference them via their Jira id or URL. It also enables you to track a separate priority and status for each treatment, and gives you auditing via Jira's issue history log.
You can choose to use any issue link type that has been defined in your Jira Cloud instance; however, the following link type is recommended:
Name: Treatment
Inward relationship: is treated by
Outward relationship: treats
If your Jira instance does not already have an issue link type named Treatment, then Risk Register will offer to create one for you as defined above.
Note that in Jira Cloud, you can disable issue linking. If issue linking is disabled in Jira, then a warning message is displayed on the app settings page.
Risk matrix appearance
This collection of options allows you to control the risk matrix appearance. The Color of empty cells option determines whether empty cells on the risk matrix are filled with gray or with the appropriate risk color. The Orientation option determines whether Impact or Probability is on the horizontal or vertical axis. Click the Flip button to swap the axes.
...
Risk impact defines the degree to which a project, product, or organization would be affected if a particular risk was realized. This list defines the impact options available, and usually contains values such as Low, Medium, High, etc. This controls what impact options are presented on the risk issue when you are assessing a risk (see Creating and Assessing Risks). When you adjust this list, the system automatically adjusts the matrix at the top of the page. Using the links supplied, you can add, remove, or rename the impacts.
...
Risk probability defines the likelihood of a particular risk being realized. This list defines the probability options available, and usually contains values such as Likely, Unlikely, etc. This controls what probability options are presented on the risk issue when you are assessing a risk (see Creating and Assessing Risks). When you adjust this list, the system automatically adjusts the matrix at the top of the page. Using the links supplied, you can add, remove, or rename the probabilities.
...