What Are Custom Fields and Field Tables?

Question

What are Jira Custom Fields and Field Tables?

Environment

Connector: Jira

Answer

Custom fields

Custom fields in Jira are user-defined fields that Fivetran can sync in addition to Jira's standard fields. For more information on how we handle different field types, see our Other Jira fields documentation.

The syncing of custom fields is enabled by default for connections set up after April 1, 2024. For connections set up before April 1, 2024, contact our support team to enable it. When enabled, consider triggering a historical re-sync. To learn more about historical re-syncs and their impact on Monthly Active Rows (MAR), see How to Trigger Historical Re-Syncs.

The Jira API often returns custom fields in raw formats, such as JSON or STRING. When you sync custom fields, we may need to fetch up-to-date values from history items, which may impact sync performance.

Custom field sync error

If we don't support a custom field's data type, you may encounter the following error during a sync:

{
    "type": "skip_processing_field",
    "message": "Couldn't find a type for field <custom_field> value..."
}

If the field is critical for your use case, , contact our support team.

Jira Field Tables

We use the following tables to capture field metadata, options, and history:

Field table name	Description
`field`	Contains the standard field data such as ID or name, if it is custom, and if it is an array field.
`issue_field_history`	We sync all values from the custom non-array fields and their history items to a single `ISSUE_FIELD_HISTORY` table.
`issue_multiselect_history`	We sync all values from the array fields and their history items to a single `ISSUE_MULTISELECT_HISTORY` table.
`field_option`	Contains data for drop-down fields / cascading select fields in Jira issues. The `parent_id` column refers to the parent value.

If a table isn't present in your destination, it means Jira didn't return that type of field data during a sync.