In this section, you can configure a risk heat map. The heat map can be used to show the level of risk resulting from the risk assessment by considering the category of probability or likelihood against the category of consequences or severity.

You can change the axis description, as well as the synchronized Jira fields. 

In the cloud version of the App, the "Risk consequence" and "Risk probability" fields are locked.


More information on the differences between cloud and server versions of the App can be found here.

Always remember to save your changes. 

Security and Access

  • Only Jira administrators can access this page.
  • Click the "wrenchicon at the top right and select "Modules" from the drop-down list. Next, go to the "Risks" tab.


Synchronized Fields

Task sources

By default, two "select list (single choice)" custom fields are created during the App installation with predefined select options. The default values are presented below:

Custom fieldSelect options

Risk probability

  • Almost none
  • Low
  • Medium
  • High
  • Very high

Risk consequence

  • Trivial
  • Low
  • Medium
  • High
  • Severe

The fields are selected per integration instance. 

Fields can be:

  • not synchronized → the value is stored in BigPicture only and isn't synchronized with any Jira field 
  • mapped to a Jira field → the Risk field value in BigPicture corresponds to the field value in the integration 

Risk value mapping

The same field can't be used to map both axes.

Risks value definition

Add and remove positions to determine what values should be visible in the Risk matrix. 

If you want the values to be synchronized with a task source (Jira), make sure that the value you add exists as a value for the mapped field.


Can the value be synchronized?

  •  a red "x" - the value exists in BigPicture only and can't be synchronized with a task source
  • a green checkmark  - the value exists for a mapped field and can be synchronized 

Why? 

A field you have used for mapping can have many values, but only the selected ones will be used in the Risk matrix. 

For example, you could remove all values except for "High" and "Very high" to create a custom risk matrix focused only on the visualization of high-risk tasks

Add a value to an axis

Click on the plus icon:

or add a new value inline:

You can either:

  • type in the value name manually (the toggle switch is "off")

  • or select from a list (the toggle switch is "on"). The list is based on the values of the mapped fields

Until you hit "Save", changes are indicated with the "To be added" label:

Remove a value from an axis

Click the trash icon on the right:

Until you hit "Save", changes are indicated with the "To be added" label:

Change axis name

You can also change the name of either axis → this is the name you will see in the Matrix of the Risk module.

Risk value order

Use the drag-and-drop mechanism to change the order of items. 

Remember to save the changes:

Saving the changes - changelog

New settings have to be saved.

The changelog can be found at the bottom of the page. Review the changelog and confirm by clicking the Save button. 

Matrix Dimensions

The dimensions of the matrix depend on the number of selected options. The default dimension is 5x5 and it is the recommended size due to the coloring of the risk levels when the heat map mode is enabled.

If you want to adjust the matrix to resemble ROAM, use ROAM as one of the axes and leave only a single option for the second one. Alternatively, you can add a risk score or severity.

To use the matrix i.e. show Jira issues on the matrix, you need to add both fields to your Jira issue screens and select one of the values.