Jira ELT Connector

An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.

Historical coverage for Jira: Backfill (Days) (backfill): The backfill setting retrieves additional data, such as comments and worklogs, for issues modified in the past X days. This ensures that the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.

Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Jira API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.

Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.

The Available streams table describes the datasets Extract can read from Jira. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.