The solution supports Jira JQL search to find Issues with risk. One common use case is to create risk reports with external visualization add-ons.
Risk issue property
All issues with a risk assessment has an issue property which is a data structure attached to the issue. See below the format on this data structure and how it is searchable with Jira JQL expressions.
{
"created": "2023-01-01"
"updated": "2023-03-04"
"risk_severity": "HIGHEST", //inherent risk
"risk_severity_value": 4,
"risk_impact": "Severe",
"risk_impact_value": 5,
"risk_probability": "Almost certain",
"risk_probability_value": 5,
"risk_residual_severity": "LOW" //residual risk
"risk_residual_severity_value": 1
"risk_residual_impact": "Minor",
"risk_residual_impact_value": 2,
"risk_residual_probability": "Rare"
"risk_residual_probability_value": 1,
}
Risk Property | Type | Value |
|---|---|---|
| date | Risk created date. If a risk is assigned to an existing Jira issue the created date is the assign date and not the issue created date |
| date | Risk update date |
| string | Unspecified, LOW, MEDIUM, HIGH, HIGHEST (default risk matrix) |
| number | 0-4 (low to high) |
| string | Unspecified, Negligible, Minor, Medium, High, Severe (default risk matrix) |
| number | 0-5 (low to high) |
| string | Unspecified, Rare, Unlikely, Possible, Likely, Almost certain (default risk matrix) |
| number | 0-5 (low to high) |
| string | Unspecified, LOW, MEDIUM, HIGH, HIGHEST (default risk matrix) |
| number | 0-4 (low to high) |
| string | Unspecified, Negligible, Minor, Medium, High, Severe (default risk matrix) |
| number | 0-5 (low to high) |
| string | Unspecified, Rare, Unlikely, Possible, Likely, Almost certain (default risk matrix) |
| number | 0-5 (low to high) |
Important: Please note that that the impact, probability and severity text is fully configurable in each risk register risk matrix.
Examples
JQL | Comments |
|---|---|
issue.property[boja_prop_issue].created >= -30d | All risks created last 30 days |
issue.property[boja_prop_issue].created >= "2023-01-01" AND issue.property[boja_prop_issue].created < "2024-01-01" | All risks created in 2023 |
issue.property[boja_prop_issue].updated >= -30d | All risks updated last 30 days |
issue.property[boja_prop_issue].risk_severity is not EMPTY | All Issues with a risk including Unspecified Severity |
issue.property[boja_prop_issue].risk_severity = "HIGHEST" | All Issues with HIGHEST Severity |
issue.property[boja_prop_issue].risk_severity_value = 4 | All Issues with HIGEST Severity using value |
issue.property[boja_prop_issue].risk_severity is EMPTY | All Issues not having a risk |
issue.property[boja_prop_issue].risk_probability = "Rare" | All Issues with probability Rare |
issue.property[boja_prop_issue].risk_probability = "Possible" AND issue.property[boja_prop_issue].risk_impact = "Medium" | All Issues with probability Possible and impact Medium |
Risk custom fields
The solution also supports risk custom fields as described here. If those fields are assigned to a risk issue screen they are searchable according to below
JQL | Comments |
|---|---|
"Inherent risk[Short text]" is not Empty AND "Inherent risk[Short text]" !~ None | All issues with residual risk. For issues without severity this field is either missing or is having value ““ or “None“ |
"Residual risk[Short text]" is not Empty AND "Residual risk[Short text]" !~ None | All issues with residual risk. For issues without severity this field is either missing or is having value ““ or “None“ |
"Inherent impact[Dropdown]" = Major | Issues with Inherent impact Major |
"Residual probability[Dropdown]" = Frequent | Issues with Residual probability Frequent |