Understanding how Jira affects MAR
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.
- There is a feature flag 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.
- Depending on if the Jira connector was set up before or after September 10, 2020, we organize some tables differently. Before September 10, we created a table for each issue field and history (ISSUE_[FIELD_NAME] and ISSUE_[FIELD_NAME]_HISTORY). After September 10, 2020 we now only create tables for ISSUE_FIELD_HISTORY and ISSUE_MULTISELECT_HISTORY and added a reference table for FIELDs.
What Contributes Towards MAR?
There are 5 primary actions that will contribute toward MAR:
- Number of issues created
- Number of times an issue field gets updated or created
- Number of users performing actions in Jira (e.g. COMMENTS table)
- After September 10, 2020, the ISSUE_FIELD_HISTORY and ISSUE_MULTISELECT_HISTORY tables are the main tables with MAR.
- Before September 10, 2020, there would be one table for each field (ISSUE_[FIELD_NAME] and ISSUE_[FIELD_NAME]_HISTORY)
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. Customers can create a Jira user that does not have access to specific objects (i.e. boards, etc.) in Jira, then Fivetran will skip these when syncing data to the destination.
- The ISSUE_FIELD_HISTORY and ISSUE_MULTISELECT_HISTORY or (ISSUE_[FIELD_NAME] and ISSUE_[FIELD_NAME]_HISTORY) tables are the main tables contributing to MAR.
- Depending on if the feature flag is enabled, customers can potentially fully sync the BOARD, PROJECT_BOARD, and ISSUE_BOARD tables.