All issue risk assessment are automatically written to eight (8) Jira read-only custom fields. As the only Jira risk solutions both editable and non-editable Jira risk risk managment solution four (4) editable custom fields are also supported. Editable Read only are text fields and editable are single select drop down options with Risk risk model 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.
| Info |
|---|
| Create Non-editable |
...
...
1. Read-only Jira risk custom fields
The Jira solution automatically creates below read-only risk custom fields must be manually created from within the app. For editable custom fields the risk model must be selected. The risk model risk matrix impact and probability values will populate the custom field drop down values.
...
Select the risk model for editable custom fields. The risk model risk matrix values impact and probability will populate the custom field drop down.
...
Non-editable Jira risk custom fields
Non-editable risk custom fields are read only text fields. Assign one or many to Jira issue screens and app risk values will be written to the fields.
...
Risk custom values in issue view
...
Editable Jira risk custom fields
Setup for editable Jira custom fields spans both setting up risk registers, risk models and finally assigning the editable custom fields to risk models. The selectable impact and probaility values in the editable custom fields are populated from the risk model risk matrix. See below steps to take.
...
Setup
...
Create project or board risk registers for the Jira issues (more info)
...
. 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.
...
Example #1 - JQL issue risk search and risks values in Jira columns
...
2. Editable Jira risk custom fields
Below four (4) editable risk custom fields are supported. They are of the type drop-down single select with the options populated from the selected risk model risk matrix (more info). The risk values are always synchronized with the internal app risk values independent if risk assessment is done from the app or Jira issue screen (how it works)
Inherent probability
Inherent impact
Residual probability
Residual impact
| Info |
|---|
Setup - easy (recommended) |
| Info |
|---|
Setup - advanced
|
How it works
On each issue risk assessment the solution checks if the issue has a screen with a editable custom field. If this it the case the solution writes the risk assessment to the custom fields.
On each time the app launces and touches a risk the risk custom fields are read. If the issue has a screen with editable custom fields the internal app risk values are updated.
Create editable Risk custom fields
Create the editable risk custom field and select the risk model to populate the custom field drop-down values.
...
Assign custom fields to Jira issue screens
The custom fields needs to be assigned to issue screens. Typically each project have a issue screen and press the “Add to Screens“ link and then select the screens.
...
Example #1: Custom fields assigned to issue screen
...
Example #2: Custom fields assigned to issue create screen
...
OLD Error Info
...
I see a risk custom field error message what to do?
If editable risk custom fields are assigned to the Jira issue screen but those drop down 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 register risk matrix values. There are two ways to remove this error message (see below).
Option 1: In global settings->custom fields. Remove the Jira editable custom fields from the risk issue project issue screen. This can be done in Jira settings or directly in the app
...
Option 2 - Assign the risk model that have the risk custom fields to your risk register. With that your risk register matrix will have the values of the custom fields
...
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)
...