Risks (App configuration)
- Comala Publishing
Security and access
Only Jira/App Admins can manage the app on the global (app) configuration level.
To access the global settings for the Risks module:
Click the wrench icon in the top right corner.
Select Modules from the dropdown.
Go to the Risks page.
Risks configuration
On the Risks page, you can set up a risk heat map. It displays the risk level based on the likelihood and severity of the risk assessment.
You can also modify the axis labels and sync Jira fields.
Task sources
By default, two "select list (single choice)" custom fields are created during app installation with predefined options. The default values are listed below:
Custom field | Select options |
|---|---|
Risk probability |
|
Risk consequence |
|
The fields are selected per integration instance.
Fields can be:
Not synchronized → The value is stored in the app only and is not synchronized with any Jira field.
Mapped to a Jira field → The risk field value in the app corresponds to the field value in Jira.
Risk value definition
The same field cannot be used to map both axes. You can use each field only once.
Probability setting
Add and remove positions to determine what values should be visible on 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.
How can you tell if the axis value can be synchronized?
A red cross () mark means the value exists in BigPicture only and cannot be synchronized with a task source.
A green () checkmark means the value exists for a mapped field and can be synchronized.
The reason is that the field you have used for mapping can have many values, but only the selected ones will be used on the risk matrix.
For example, you could remove all values except "High" and "Very high" to create a custom risk matrix focused only on visualizing high-risk tasks.
Customize the risk matrix
Add a value to the axis
To add a new risk value:
Click the plus icon below the respective axis (named “Probability” and “Consequence” by default). Alternatively, you can add a new risk “Probability”/“Consequence” value inline.
Name the new value.
You can either type the value name manually (when the toggle switch is "off") or select it from a list (when the toggle switch is "on"). The list is based on the values of the mapped fields.
Save changes to add new values labeled “To be added.”
Remove a value from an axis
Consequence and probability values set for a risk need to be consistent with the configuration of both axes. If you delete a consequence or probability value from the axis configuration, a risk that has such a value set is removed from both the matrix and table view.
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.
Order risk values
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, 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.
Need support? Create a request with our support team.
Copyright © 2005 - 2025 Appfire | All rights reserved.