As the only Jira risk solutions both editable and non-editable Jira risk custom fields are supported. Editable are single select drop down options with Risk matrix impact and probability values and non-editable are read-only text fields for all risk values. Editable custom fields make it possible to enforce risk assessment on Jira issue creation outside the app.
Read-only Jira risk custom fields
The solution automatically creates below read-only risk custom fields. All risk assessments are written to those custom fields and they can be used for e.g. issue JQL search, reporting and added to Jira columns.
#1 Example JQL issue risk search and risks values in Jira columns
Editable Jira risk custom fields
Setup for editable Jira custom fields involves both setting up risk registers, risk models and finally assigning the editable custom fields to a risk model. The impact and probability custom fields drop down values are populated from the assigned risk mode.
Setup
Create project or board risk registers for the Jira issues (more info)
Create risk model (more info)
Assign risk registers to the risk model (more info)
Editable custom fields
Create editable custom fields (see section above)
Assign custom fields to Jira issue screens (see picture below)
Assign custom fields to Jira issue screens
Example: Custom fields assigned to issue screen
Example: Custom fields assigned to issue create screen
I see a risk custom field error message what to do?
If editable risk custom fields are assigned to an issue screen the app tries to set the custom fields impact and probability values. Below error message is shown if the custom fields values are not matching the issue risk matrix values. There are two ways to remove this error message.
Option 1: In global settings->custom fields. Remove the editable custom fields from the risk issue project issue screens. With this the app is not trying to write risk values to the custom fields
Option 2: The issue project risk register is not assigned to the editable risk custom fields risk model. So assign the risk register to the risk model (more info)
