Issue Summary

In Jira Cloud, Formula custom fields cannot reference other existing formula custom fields within their calculation expressions. When users or administrators attempt to build modular, tiered, or cumulative calculations (such as summing or multiplying the results of two intermediate formula fields), the formula editor fails to recognize the existing formula fields as valid inputs.

Steps to Reproduce

1. Navigate to Jira Settings > Issues > Custom Fields.
2. Create two separate Formula custom fields with numeric outputs (e.g., Formula Field A and Formula Field B).
3. Create a third Formula custom field (e.g., Total Calculated Field) with output set to Number.
4. In the formula editor of the third field, attempt to reference the two existing formula fields in a calculation.

Expected Results

• When typing "{", existing formula custom fields appear in the auto-complete suggestion list alongside standard fields.
• The formula syntax validator accepts the referenced formula fields, successfully saves the configuration, and dynamically evaluates the combined calculation on work items.

Actual Results

• Existing formula custom fields are excluded from the "{" suggestion dropdown.
• Manually typing the formula field names causes the formula editor to display the validation error:

  Formula error: 2 invalid fields

• The field configuration cannot be saved.

Business Impact

• Blocked Migration from Automation: Many organizations adopted Formula Fields to decommission high-maintenance Jira Automation rules. The inability to nest formulas forces teams to retain automation rules solely to compute totals.
• Automation Quota Consumption: Retaining automation rules to recalculate and sync field values consumes monthly automation execution limits that could otherwise be saved.
• Administrative Maintenance & Duplication: Without the ability to reference intermediate formula fields modularly, admins must manually duplicate complex underlying formulas across multiple fields, increasing maintenance overhead and the risk of calculation discrepancies.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.