All issue risk assessment are automatically written to eight (8) Jira read-only custom fields. As the only risk managment solution four (4) editable custom fields are also supported. Read only are text fields and editable are single select drop down options with risk model risk matrix impact and probability values. Editable custom fields make it possible to enforce risk assessment on Jira issue creation outside the app.
| Info |
|---|
...
1. 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.
...
Example #1 Example - 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)
...
| Info |
|---|
Setup - easy (recommended) |
...
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.
...
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
...