Administering the application
Customization of the application for your organization is accomplished through several administration pages.
Accessing the administration pages
Select the gear icon () in the top right-hand of the screen and then select Apps. The Risk Register App menu appears in the left-hand panel with these links:
Each link is described below.
This page appears when you install the application. It describes the various steps you must undertake to initialize the application for use. It is primarily a prompt to remind you to configure the pages described below.
This page enables you to configure the appearance and behavior of the application. The following configuration options are available:
Risk (issue) types
These dropdown menus determine when and how various options are presented to users:
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. Particular projects can override these defaults.
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. 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 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:
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.
Old releases had an option to "enable" risk management. With the current release, users no longer explicitly enable risk management, neither at the app level nor at the project level. Whereas enabling risk management for a project previously generated an 'implicit' risk register, that is no longer the case. Instead, you explicitly create the risk registers that you want. For customers using the older version, any implicit risk registers were converted to explicit risk registers for any projects that had risk management enabled at the project level (overriding the app settings), or which contained one or more risks.
This page defines the risk model used to assess the level of risk for each risk you create. The model is in the form of a matrix. The axes are Impact and Probability, while the cells define the level of risk. You can adjust the level of risk for a cell by selecting the drop-down box inside it.
There are three tabs beneath the matrix, defining Impacts, Probabilities, and Levels of risk.
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. 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. 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.
Levels of risk
Level of risk is calculated on the risk matrix using the impact and probability of the risk. This list defines the levels of risk available, and usually contains values such as Low, Medium, High, etc. This controls what options are presented in the cells on the risk model above. Using the links supplied, you can add, remove, or rename the levels of risk.
Clicking on this link opens up the ProjectBalm support portal, which allows you to search our knowledge-base and also raise a service request.