Page Comparison

enables you to configure the appearance and behavior of the application. The following configuration options are available:

Risk (issue) types

These drop-down menus determine when and how various options are presented to users:

Image Added

Note the following:

• If an issue has a risk assessment attached to it, that issue will appear in any risk register based on those projects or filters that include the issue (though a sub-filter can be used to exclude it).

• 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 are 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.

• 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 so that it no longer is of the primary risk type nor a supplementary risk type.

• The primary risk type and supplementary risk types defined here represent defaults. Individual projects can override these defaults.

Risk treatment

This drop-down 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. If you leave the field blank, then treatments will not appear on the risk register page.

Image Added

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 in the main risk register view. 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 section 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. 

Image Added

Risk link availability

This option allows you to control whether a link to risk register from the project sidebar is enabled by default in the system. If the switch is off, no link will appear unless you have created a risk register for that project. This setting can be overridden on the risk register project settings page.

Image Added