Summary:

Customer Impact / Use Case

Ref.: Jira Cloud Platform changelog

• Partners are extending Jira Service Management portals and other UIs via Forge/Connect to provide richer presentations of formula-type fields.

• To keep the portal experience consistent with Jira’s configuration, apps must be able to:

• • Understand how the formula is defined.
  • Respect configuration options that influence how the field should be displayed or interpreted.
• Without an API surface for formula field configuration, partners:
  • Cannot reliably support these new field types in their apps.
  • Must resort to manual configuration duplication and synchronization, which is error‑prone.
  • Have limited ability to build advanced or dynamic experiences around formula fields.

Partners have requested that these formula field settings be available via a supported API so they can align their portal extensions with the field’s configuration. They can currently only see the required settings via GraphQL, but the scopes needed are not exposed for Forge, making this unsupported for Marketplace apps.

Steps to Reproduce

1. In Jira Cloud, create a Number formula custom field (or other formula-type field introduced in CHANGE‑2714):
   Jira Cloud Platform changelog
2. Configure the field in the Jira UI (e.g. set the formula, options, and any advanced settings).
3. From a Forge or Connect app:
   1. Use the Jira issue REST API (e.g. GET /rest/api/3/issue/{issueIdOrKey}{}) to retrieve an issue using this formula field.
   2. Attempt to retrieve the field configuration (formula definition and other settings) through any documented REST API.
   3. Attempt to retrieve the same configuration via Atlassian GraphQL using Forge (with all currently available scopes).

Expected Results

• There is a public, documented API (REST or productized GraphQL) that allows Forge and Connect apps to:
  • At minimum, read the configuration of formula custom fields, including:
    • The formula expression itself.
    • Any relevant configuration options/flags that affect how the field is presented or evaluated.
  • Ideally, also write/update that configuration, subject to appropriate permissions.
• Forge/Connect apps can request the necessary OAuth/scopes to access this configuration in a supported way.
• Marketplace apps can reliably mirror or respect formula field configuration in Jira Service Management portals and other custom UI surfaces.

Actual Results

• Only the calculated values of the formula field are accessible via the existing Jira REST APIs (e.g. when retrieving an issue).
• The configuration of the formula field (formula expression and related settings) is:
  • Not exposed via any documented Jira Cloud REST API.
  • Only visible via internal GraphQL views.
  • Not accessible from Forge apps because the required GraphQL scopes are not available for Forge/Connect.

• As a result, Forge/Connect apps cannot programmatically discover or respect the formula configuration, and can only work with the final evaluated value.

 

Workaround

• No known full workaround.

• Apps can:

• • Read and display the calculated value of the formula field via existing issue REST APIs.

• But they cannot:

• • Read the underlying formula expression or configuration.

• • Adapt portal or app UI behavior based on those settings.

• • Keep any configuration mirrored in sync without manual duplication by admins.