Jira is a bug tracking, issue tracking and project management software.
|Custom data||check||Custom issue fields. We do not support all custom field types. Contact support if you’d like to sync specific custom field types.|
|Data blocking||check||Column level|
|History||check||We sync issue field changes in the following manner:
• to the
• to a
|Fivetran data models||check||Get the models: source / transform|
Follow our step-by-step Jira setup guide to connect Jira with your destination using Fivetran connectors.
We capture value changes that occurred between syncs.
ISSUE_FIELD_HISTORY table stores historical changes for non-array fields, while the
ISSUE_MULTISELECT_HISTORY stores historical changes for array fields. When we first sync an issue, we write the initial field values to either of the history tracking tables, depending on the field type. Also, we write the issue creation timestamp to the
time column of the relevant history tracking table. Once the field is changed, we write the new field value to the relevant column and the change timestamp to the
time column of the relevant history tracking table.
Jira connectors use JQL (Jira Query Language) to make incremental updates on issues.
The issue field value can be a primitive value or a complex object with its own fields. In the latter case, the issue table stores the object identifier and the corresponding dimension tables store other object fields.
Issue sync mode
You can select the projects whose associated issues you want to sync:
- if you choose From all projects, the connector syncs the issues from all projects and you can browse through them. The connector syncs new projects once they are available. No additional action on your part is required.
- if you choose From selected projects, the connector only syncs the issues that belong to the projects selected in the setup form.
NOTE: If you deselect a project, the connector stops syncing its issues. The issue sync mode applies to all Jira connectors, whichever schema they use.
Jira connector updates the following groups of tables in full once a day:
SECURITY_SCHEME_LEVELYou can manage syncing of these tables on the Schema tab of your Fivetran dashboard.
General sync limitationlink
Since Jira does not explicitly provide information on object field value changes, we are only able to update field values that were changed in Jira when the
issue endpoint response contains data related to the relevant object. During the sync, we first call the
issue endpoint. Then, as next sync steps, we call all the endpoints corresponding to the issue fields contained in the
issue endpoint response. Lastly, we update the old values of the relevant issue fields with the new values from the endpoint responses.
For example, let’s assume the
issue endpoint response contains an issue item with the
status field whose value (
123. We then call the
status endpoint and, for a status item with
id = 123 in the response, the value of the
name field is
resolved. Later, in Jira, the name of the status with
id = 123 is changed to
fixed. We are only able to update the value of the
name column to
fixed in the
STATUS destination table once we sync a change in your Jira source that includes an issue with the
status field whose
123 and the updated
name value is
User data sync limitationlink
Fivetran may not sync complete data for the
username columns because the Jira REST API may not return the corresponding data. Due to their compliance with the GDPR laws, Atlassian restricts the visibility of user personal data based on the user profile privacy settings. Read Atlassian’s Deprecation notice and migration guide for more information.
NOTE: This limitation applies to Jira Cloud installations.
This schema applies to Jira connections set up after September 10, 2020.
FIELD table contains system information about the Jira issue field such as ID, name (as it is displayed in Jira UI), whether it is custom, and whether it is an array field.
ISSUE table contains values of non-array system fields.
ISSUE_FIELD_HISTORY table contains custom field values, their historical changes, and historical changes of non-array system fields. See the Historical changes section for details about how we track historical changes.
ISSUE_MULTISELECT_HISTORY table contains array field values and their historical changes.
NOTE: The actual field records have the
is_actualcolumn value set to
author_idcolumn stores the identifiers of the users who made changes to a given issue.
This schema applies to Jira connections set up before September 10, 2020.
Custom fields informationlink
Jira custom field types mapping
|Jira type||Destination table / Primitive type|
NOTE: The value of each level of the cascading select field is represented as a single entry in the
FIELD_OPTIONtable. The child value entry contains a link to the parent value in the
Jira Service Management (formerly Jira Service Desk) custom field types mapping
|Jira type||Destination table / Primitive type|
Click External Link in a table header in the ERD to navigate to the Jira API documentation section that describes the corresponding endpoint.
Custom fields warning log
If your Jira object contains a custom field that we don’t support, you will see the
skip_processing_field Warning during the initial sync.
Custom field feature request
If you don’t see a custom field you’d like to sync listed, reach out to our Support Team.