Jira Connector Overview
- The Jira connector pulls from the BOARD and ISSUE endpoint APIs. The schema output from the Jira connector is predefined and customers cannot uncheck any of the tables synced by our Jira connector. Jira’s own ERD is very complex and Fivetran simplifies these objects into more analytics-friendly relationships.
- It's possible to request to fully sync the BOARD, PROJECT_BOARD, and ISSUE_BOARD tables, which enables the connector to resync the tables to include all issues on the boards. Please contact the Support team for help enabling this feature.
- Depending on if the Jira connector was set up before or after September 10, 2020, we organize some tables differently. Prior to September 10, 2020, we created a table for each issue field and history (
ISSUE_[FIELD_NAME]_HISTORY). Since September 10, 2020, we only create tables for
ISSUE_MULTISELECT_HISTORYand added a reference table for FIELDs.
What Contributes Towards MAR?
There are 5 primary actions that will contribute toward MAR:
- The number of issues created.
- The number of times an issue field gets updated or created.
- The number of users performing actions in Jira (e.g., the
- After September 10, 2020, the
ISSUE_MULTISELECT_HISTORYtables are the main tables with MAR.
- Before September 10, 2020, there would be one table for each field (
Managing MAR for this Connector
- There is not much you can do to reduce the MAR from this connector since you cannot uncheck any of the tables. It's possible to create a Jira user that does not have access to specific objects (i.e. boards) in Jira, then Fivetran will skip these when syncing data to the destination.
ISSUE_[FIELD_NAME]_HISTORY) tables are the main tables contributing to MAR.
- Depending on whether the feature has been manually enabled by the Support team, you can potentially fully sync the BOARD, PROJECT_BOARD, and ISSUE_BOARD tables.
- Fivetran Jira Connector
- New Jira ERD
- Old Jira ERD
- Consumption Based Pricing Overview
- Jira Release Notes