You can change the terminology and rename modules. To avoid confusion, check the module icon, which is unalterable.
Use this module to assess risk probability and consequence, and show your risks on the heat map.
The risks module consists of two main elements:
- Customizable risk heat map
- Customizable risk list (register)
The dimensions of the heat map depend on the number of selected options. The default dimension is 5x5, and it is the recommended size because of the coloring of risk levels with the heat map mode enabled.
Any issue type can be displayed on the heat map, but to do so, you need to add the "Risk probability" and "Risk consequence" fields to your issue screens first. You can synchronize your Risks with other fields. To change the field mapping, go to configuration > Risks Admin permissions are required.
To use the heat map, i.e., show Jira issues on the heat map and in the register, you need to add both fields to your Jira issue screens and select one of the values.
The Risk level is determined by using two fields, Risk probability, and Risk consequence. By default, the App uses custom fields created during the installation, but you can use your own fields as long as a "Select list (single choice)" type of fields are used.
If you want to adjust the heat map to resemble ROAM, use ROAM as one of the axes and leave just a single option for the other one. Alternatively, you can add a risk score or severity.
You can change the displayed columns of the Risk table.
The main features of this module are described in the table below.
Add new issues to be displayed on the heat map. Any Jira issue can be presented on the heat map, but we recommend creating a separate issue type to represent the identified risks.
There are three options available:
Note that although the Risks module is now available also on Boxes with no Scope, it does not allow you to create new risks (the "Add" button is greyed out).
Change the view options to include more information on the Risk heat map or show additional features:
To unlock the export features, install the BigTemplate App from the Atlassian Marketplace.
Export is disabled in case there is no risks to be exported.
|Quick filter||Add your favorite filters to the header and filter the risks from the list and the heat map.|
|Date range filter||Narrow the list of displayed risks to a particular time period using the mapped Start and End date fields.|
|Axis description||You can change the axis description in the App's configuration. Jira admin access is required.|
|Risk field's values||The module uses the "Select-list (single choice)" field type, which means you need to preconfigure the select options (Jira Admin access required).|
|Customizable risk card|
The layout of the card can be modified in the Box configuration section.
|Search box||Use the text search or a JQL filter to find the risks.|
|Risk card picker||Change the layout of your risk cards and mark your favorite ones using a star.|
Customizable risk table which can display any issue type with Risk probability and Risk consequence value set.
Modify the columns of the risk table by adding available Jira fields.
Edit (Use inline editing to update field values) or Delete Risks – when risk is deleted, it's only removed from the Risks module, i.e., the values of Risk probability and consequence are cleared, and the risk will not appear on the list.
Sort your risks in ascending or descending order based on the fields added to the risk card.
Inline edit fields Text fields and number fields are displayed on the Risk cards and in the Risk table.
|Open in Lightbox||Use the presentation mode to zoom in on the selected risk card.|
Risks in the "None-scope" Boxes
Risks module in the Boxes with no scope have access to risks collected from its child Boxes:
- from all own-scope Boxes one level down (direct children)
- from all sub-scope Boxes (all levels down) of the own scope Boxes mentioned above.