Skip to main content

Field rendering problems

If a field does not look right in an export, this page helps you diagnose why.

Safe fallback​

Unknown field types render with a safe fallback as readable text rather than failing the export. So a "plain" looking value usually means the type is not yet specially supported.

Unsupported field types​

Some third-party custom field types may only render via the fallback. See Custom fields for how the field-renderer registry works.

Custom field quirks​

  • Confirm the field has a value on the issue.
  • Confirm you can see the field in Jira (exports run as you).
  • Check the binding in the template — see Binding components to Jira data.

How to report​

When reporting a rendering issue, include the field type, an example issue, and the template used. See Getting help.