Custom Fields and Field Tableslink

Updated 11 days ago

Questionlink

What are Jira Custom Fields and Field Tables?

Answerlink

Jira Custom Fieldslink

NOTE: Reach out to Fivetran Support to enable the sync of all Jira Custom Fields. They are not synced by default as some fields are returned in their raw format.
After custom fields sync is ebabled, historically sync your Jira connectors. Historical sync will incur Monthly Active Rows (MAR) for all rows.

Custom fields in Jira is what allows syncing unknown fields and their history items in raw format (JSON, string). During a sync, custom fields can have negative impact because Fivetran fetches the current values from the history items if they exist.

During a historical sync you might receive a warning (custom field number varies):

    "type":"skip_processing_field",
    "message":"Couldn't find a type for field customfield_10007 value...
content_copy

This warning means that Fivetran doesn't support this data type. If it's a critical field for your use of the connector, contact Fivetran Support.

Jira Field Tableslink

Fivetran has the following Jira field tables:

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.