Jira Cloud Connector

Sync Jira Cloud issues, projects, users, workflows, comments, worklogs, and history into your warehouse.

SourceCommunity

Evaluating against Fivetran? See how Supaflow handles Jira Cloud pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Email + API Token Authentication

Connect with an Atlassian email and API token. The connector is read-only and never writes back to Jira; the account only needs Browse Projects permission on the projects you want to sync.

Reliable Incremental Issue Sync

Issues sync incrementally after the initial load, with boundary-safe handling for Jira Cloud timestamp precision so updates are not silently missed.

Custom Field Discovery

Discovers standard and custom Jira fields with their Atlassian-declared types so nullable fields and renamed custom fields remain stable in the warehouse.

Issue Details and History

Optionally sync components, versions, issue links, subtasks, transitions, comments, worklogs, and changelog history alongside issues.

Field Selection for Large Sites

Select only the issue fields and related records you need to reduce payload size and sync time on large Jira Cloud sites.

Lookback for Late-Arriving Updates

An optional lookback window re-reads a recent slice of Jira updates, which helps with late-arriving changes on busy Jira Cloud sites.

Supported Objects

Jira Data

Issues

Issues with configurable related records such as components, versions, links, subtasks, transitions, comments, worklogs, and history.

Projects

Projects visible to the authenticated account.

Users

Active and inactive user accounts visible to the authenticated account.

Workflows

Workflow definitions used for project and issue status reporting.

Issue Details

Components

Components attached to issues.

Fix versions

Fix version links.

Affected versions

Affected version links.

Issue links

Relationships between Jira issues.

Subtasks

Subtask references.

Transitions

Available issue transitions.

Comments

Comments on issues.

Worklogs

Worklog entries on issues.

Changelog history

Issue history and status-change records.

Not synced today

Jira Software and admin objects

Boards, sprints, dashboards, permission schemes, and other admin configuration objects are not part of this connector today. Jira Server and Data Center are also not supported.

How It Works

Create an Atlassian API token

Create an API token for the Atlassian account you want the connector to use. Give the token a clear label and copy it once -- Atlassian will not show it again.

Enter the subdomain and credentials in Supaflow

Enter your Jira Cloud site, the Atlassian account email, and the API token. Credentials are stored encrypted.

Configure advanced settings

Optionally adjust schema refresh frequency and add a lookback window for late-arriving issue updates.

Test and save

Click Test & Save. Supaflow validates the credentials, saves the source, and runs schema discovery.

Use Cases

Engineering velocity and cycle-time reporting

Land issues and issue history, then compute lead time, cycle time, and throughput per project or team.

Issue and worklog time tracking

Sync worklog data alongside issues to build time-by-project or time-by-assignee reports, even when in-product time-tracking views are limited.

Comment and mention analysis

Land issue comments with author and timestamp metadata. Combine them with warehouse enrichment to classify support issues, flag escalation language, or summarize long threads.

Frequently Asked Questions

Does Supaflow support Jira Server or Jira Data Center?

No. The connector supports Jira Cloud only. Email support@supa-flow.io if Jira Data Center support is important for your evaluation.

How does Supaflow handle Jira custom fields?

Supaflow discovers Jira custom fields and their Atlassian-declared types during schema refresh. Stable Jira field IDs are preserved, so renaming a custom field in Jira does not break existing warehouse columns.

What permissions does the Atlassian account need?

Only Browse Projects on the projects you want to sync. Administer Jira is not required. For long-term stability, create a dedicated service account rather than using an individual user’s token -- if the individual leaves and the account is deactivated, the pipeline breaks.

Can I sync boards, sprints, epics, or filters?

Not today. The connector focuses on issues, projects, users, workflows, and issue-related records. Email support@supa-flow.io if boards, sprints, epics, or filters are important for your evaluation.

How does incremental sync avoid missing Jira updates?

Supaflow handles Jira Cloud timestamp precision conservatively. Some issues may be re-read across sync boundaries, but that is intentional and prevents missed updates.

Does the connector handle Jira rate limits?

Atlassian applies rate limits per site and plan. For very large sites, schedule syncs off-hours and select only the issue fields and related records you need to reduce API load.

Can I run the Jira pipeline natively inside Snowflake?

Yes. In Snowflake Native App mode, Supaflow runs the pipeline data plane inside your Snowflake account via Snowpark Container Services. See our Snowflake Native ETL guide for details.