/
Red Warning in BigPicture Risks Configuration Due to Non-Global Contexts in Jira Data Center

Red Warning in BigPicture Risks Configuration Due to Non-Global Contexts in Jira Data Center

Key details

Customer environment: Jira Data Center 10.3.16, BigPicture 8.53.0, license tier 3000, customer location: Switzerland. Symptom: a red warning appears in BigPicture Risks configuration. Root cause: Risk Probability and Risk Consequence custom fields were configured with project-specific contexts; these fields support only a global context. Resolution: change both fields’ contexts to Global (all projects).

General

This article documents a known configuration pitfall in Jira Data Center when enabling or using the BigPicture Risk Management module. If the dedicated custom fields for risk scoring do not use a global context, BigPicture cannot reliably read or populate suggested values, leading to warnings and non-functional risk parameters.

AI Insights

Automated analysis of the ticket data indicates the warning consistently appears when either Risk Probability or Risk Consequence lacks a global context. In such cases, BigPicture’s configuration UI may also show empty suggested value lists or attempt to fetch configuration endpoints that return 404 when scoped contexts exclude the current project.

Description

A customer on Jira Data Center reported a persistent red warning in the BigPicture Risks configuration. The issue was traced to Jira custom field contexts: the required fields Risk Probability and Risk Consequence had project-specific contexts instead of global. BigPicture requires these fields to be globally available so risks can be evaluated consistently across boxes and projects.

Draft: Why Is There a Red Warning in BigPicture Risks Configuration on Jira Data Center?

Overview

When Risk Probability and Risk Consequence are restricted to specific projects, BigPicture cannot access or render their option sets everywhere they are needed. This causes a red configuration warning and, in some cases, empty or failing suggested-value lookups in the Risks module.

Background

BigPicture’s Risk Management relies on two Jira custom fields to compute risk exposure and enable consistent risk assessment across initiatives. On Jira Data Center, these fields must use a global context so they are present and valid for all relevant issues. Project-specific contexts fragment availability and option IDs, which prevents BigPicture from resolving risk parameters reliably.

Key Points

Symptoms

  • Red warning banner in BigPicture Risks configuration panel.

  • Suggested values section for Risk Probability or Risk Consequence appears empty, cannot be saved, or the configuration UI intermittently fails.

  • Network tab may show 404 responses for endpoints fetching field options when context excludes the project/issue type.

Root Cause

Risk Probability and Risk Consequence were configured with project-specific contexts. These fields support only a global context for proper operation with BigPicture.

How to Verify Field Contexts in Jira Data Center

  1. Go to Jira Administration > Issues > Custom fields.

  2. Search for “Risk Probability” and “Risk Consequence”. Open the ••• menu > Contexts and default value.

  3. Check the Contexts section: if you see one or more project/issue-type scoped contexts, the fields are not global.

  4. Confirm whether option sets differ across contexts. Inconsistent options are a strong indicator of non-global configuration.

Resolution: Set Both Fields to Global Context

  1. In Jira Administration > Issues > Custom fields, open “Risk Probability” > Contexts and default value.

  2. Remove project-specific contexts or consolidate into a single Global context (All projects, All issue types). Ensure one context remains and it is Global.

  3. Repeat the same for “Risk Consequence” so both fields are Global.

  4. Verify option sets are present and meaningful for both fields after consolidation.

  5. Return to BigPicture > App Configuration > Risks and reload the page. The red warning should disappear, and suggested values should load.

Troubleshooting Steps

  • Clear BigPicture caches by reloading the configuration page and, if needed, reindexing Jira custom field contexts.

  • Use a test project/issue to validate that both fields appear on the screen and can be set; then check BigPicture Risks for correct rendering.

  • Use browser DevTools > Network to confirm option endpoints return data for both fields after making them Global.

Validation Checklist

  • Risk Probability context = Global (All projects, All issue types).

  • Risk Consequence context = Global (All projects, All issue types).

  • BigPicture Risks configuration shows no red warnings.

  • Suggested values load correctly and can be saved.

Communication Best Practices

  • Acknowledge the warning and explain it results from Jira field contexts not being global. Avoid attributing the issue to app defects before verifying contexts.

  • Guide administrators to set both fields to Global and confirm in the Risks configuration that values render. Offer to stay on the call/chat while they adjust contexts.

  • If customers require different options by project, clarify that Risk Probability and Risk Consequence must remain global for BigPicture; customization can be achieved via separate project fields or labels, but not by scoping these core fields.

References