Risk Register is available on the cloud version of Jira as well as the server version of Jira. Although the application provides very similar functionality across both platforms, there are some differences due to differences in architecture and feature-set maturity. The following table describes those differences. Please note that the versions for Data Center and Server are functionally identical.
Feature | Server | Cloud |
|---|---|---|
Admin panel automatically sets up fields, issue types, screens, controls, treatments, and workflows for you | Yes | No |
Supports multiple risk models per server instance | Yes | No |
Supports “health check” to determine if system is configured correctly | Yes | No |
Ability to define primary and supplementary risk types for projects | No | Yes |
Ability to create multi-project risk registers | No | Yes |
Ability to add risk information to any issue type | Yes | Yes |
Includes Treatment Plan, Contingency Plan, and Realization fields on risk screen | Yes | No |
Creates custom risk management workflow for project | Yes | No |
Can create dashboard gadget assigned to a filter | Yes | No |
Can create a matrix report | Yes | No |
Can integrate risk matrix gadget in Confluence | Yes | No |
Impact and Probability Custom Fields | Custom fields are editable and can appear on the create screen and be used in Jira automation | Custom fields are read-only and cannot appear on the create screen or be used in Jira automation |
Can view risks across projects | Yes - using dashboard gadget assigned to a filter | Yes - using multi-project risk registers |