Currently, the Jira Expressions Evaluate API (/rest/api/2/expression/eval) does not support the expand=renderedFields parameter, unlike the Search API. As a result, when evaluating expressions that reference custom fields—especially Forge custom fields that use field providers for decryption or formatting—the API only returns the raw stored value (such as an encrypted string), not the rendered or user-facing value that would be shown in the Jira UI or returned by the Search API with expand=renderedFields.

This limitation blocks Marketplace partners and customers from building automations, integrations, and reporting solutions that depend on accessing the actual rendered value of custom fields via Jira Expressions. For example, third-party apps like Rich Filter cannot display decrypted or formatted values for Forge custom fields, and any workflow that relies on the Evaluate API is limited to raw data.

This feature request is to bring the Evaluate API to parity with the Search API by supporting expand=renderedFields (or equivalent functionality), so that consumers can retrieve the formatted, decrypted, or provider-rendered values for all fields—including Forge custom fields—when evaluating Jira Expressions. This will enable richer automation, reporting, and integration scenarios, and ensure consistency across Jira’s APIs.