Jira Cloud Source

Connect Jira Cloud as a source to sync issues, projects, users, and workflows from your Atlassian instance.

For an overview of capabilities and use cases, see the Jira connector page. To run pipelines natively inside Snowflake, see Snowflake Native ETL.

Prerequisites

Before you begin, ensure you have:

• A Jira Cloud site at an atlassian.net subdomain
• An Atlassian account with Browse Projects permission on every project you want to sync
• An Atlassian API token from id.atlassian.com/manage-profile/security/api-tokens

Supported Objects

Top-Level Resources

Object	Sync Mode	Description
Issues	Incremental	Every issue visible to the authenticated account. Includes nested child tables (see below).
Projects	Full Refresh	All projects visible to the authenticated account.
Users	Full Refresh	All Jira users, including inactive accounts.
Workflows	Full Refresh	Workflow definitions across your site.

Child Tables of Issues

When you select the Issues resource, the following child tables are materialized automatically. Unselected children are skipped to reduce API load.

Child Table	Description
Components	Components attached to issues.
Fix Versions	Versions an issue is scheduled to ship in.
Versions	Affected versions on an issue.
Issue Links	Links between issues (blocks, duplicates, relates to, etc.).
Subtasks	Subtask references on parent issues.
Transitions	Available workflow transitions for each issue.
Comments	Every comment on every issue with author and timestamp.
Worklogs	Time-tracking entries on issues.
Changelog Histories	Field-level change history (status transitions, assignee changes, etc.).

Not Yet Supported

The v1 connector does not sync boards, sprints, epics as a separate entity, filters, dashboards, permission schemes, notification schemes, issue types as a separate entity, priorities, resolutions, custom field options, or project roles. In Jira Software company-managed projects, epic-relationship data is typically carried on the Epic Link custom field on each issue; team-managed projects use a native parent relationship that the v1 connector does not specifically model.

Jira Server and Jira Data Center (self-hosted Jira) are also not supported -- this connector targets Jira Cloud only.

Contact us with the objects you need -- expansion is prioritized by customer demand.

Incremental Sync

Issues sync incrementally on the updated timestamp -- only changed issues are fetched on each run. Projects, Users, and Workflows run full refresh (see Supported Objects).

Jira's JQL accepts minute-level timestamps only, so the cursor is stored at minute precision. Edits made within the same minute as the last sync may be re-read on the next run.

Authentication

Supaflow authenticates with basic auth: your Atlassian account email plus an API token. No OAuth flow is involved. This matches Atlassian's documented approach for server-to-server access to the Jira REST API.

Create an API Token

1. Sign in to id.atlassian.com/manage-profile/security/api-tokens with the Atlassian account you want the connector to use
2. Click Create API token
3. Give it a descriptive label (e.g., "Supaflow integration")
4. Copy the token once -- Atlassian will not show it again

Permissions

The connector is read-only and never writes, transitions, or modifies Jira state. The account needs only:

• Browse projects on every project you want to sync

For long-term stability, use a dedicated service account rather than an individual user's token. If the individual leaves the org and their account is deactivated, the pipeline breaks.

Configuration

In Supaflow, create a new Jira source with these settings:

Jira Subdomain*

Your Jira Cloud subdomain. Either the bare subdomain or the full .atlassian.net hostname is accepted.
Example: mycompany

Email*

The Atlassian account email that owns the API token.

API Token*

The API token you created at id.atlassian.com.
Stored encrypted

Schema Refresh Interval

How often to re-discover your Jira schema (including custom fields) before running.
Options:

• 0 - Refresh before every pipeline execution. Recommended if custom fields change routinely.
• -1 - Disable refresh. Use for static schemas.
• Positive value - Refresh interval in minutes (e.g., 60 = hourly, 1440 = daily).

Default: 0

Lookback Period

Seconds to roll the incremental cursor back on each run of Issues. Useful if you observe late-arriving updates due to Jira Cloud's eventual consistency.
Default: 0 (no lookback)

Test & Save

After configuring your authentication, click Test & Save to verify your connection and save the source.

Rate Limiting

Atlassian applies API rate limits to the Jira Cloud REST API. Supaflow handles transient rate limiting automatically with retry and backoff, but very large Jira sites may need off-peak scheduling or narrower field and child-table selection to reduce API load. See Atlassian's rate limiting guide for current limits.

Schema Evolution

Jira schemas are re-discovered on each run (or on the cadence set by Schema Refresh Interval).

• New custom fields appear in subsequent syncs once the schema refresh runs
• Renamed custom fields keep their underlying field ID, so the destination column name does not change
• Deleted custom fields are no longer populated; the column remains in the destination
• New top-level resources (e.g., future Jira endpoints) require a connector update and are not discovered automatically

Troubleshooting

Authentication failed

Problem:

• "Jira authentication failed" or 401 error on Test & Save

Solutions:

1. Confirm the email matches the Atlassian account that owns the token, not a group or team alias
2. Regenerate the API token at id.atlassian.com/manage-profile/security/api-tokens and paste the new token
3. Confirm the subdomain is just the company name (e.g., mycompany) or the full atlassian.net hostname -- do not include https://
4. Verify the account is not suspended by signing in to Jira in a browser with the same email

Only some projects appear

Problem:

• The Projects stream returns fewer rows than expected
• Some projects are missing from schema discovery

Solutions:

1. Confirm the authenticated account has Browse projects permission on the missing projects -- the connector only sees projects the account can see
2. If your org uses project-level permissions, switch to a service account with broader read access
3. Private projects created after the connection was established appear on the next schema refresh

Issue updates take time to appear

Problem:

• An issue was edited in Jira but the change is not in the destination on the very next sync

Solutions:

1. Jira Cloud is eventually consistent -- edits can take a short period to become queryable via the REST API. Wait for the next scheduled sync.
2. If you consistently miss late-arriving updates, set Lookback Period to 60 -- 300 seconds
3. Edits made within the same minute as the last sync may wait for the next run because Jira's search API accepts only minute-level timestamps

Custom fields are missing

Problem:

• A custom field visible in Jira has no matching column in the destination

Solutions:

1. Set Schema Refresh Interval to 0 to force a fresh schema discovery on the next run
2. In the pipeline wizard, deselect and reselect the Issues resource to pick up recently added fields
3. Confirm the authenticated account has access to the custom field in Jira -- fields restricted to other users will not appear

Changelog or worklog is empty

Problem:

• The Changelog Histories or Worklogs child table is empty for issues that have history or worklogs in Jira

Solutions:

1. Confirm you selected the child table in the pipeline wizard -- unselected children produce no rows
2. Verify the issues you are syncing actually have visible history or worklog entries for the authenticated account

Jira Server or Data Center site

Problem:

• Your Jira is self-hosted at jira.yourcompany.com, not on atlassian.net

Solutions:

1. This connector targets Jira Cloud only. Self-hosted Jira Server and Jira Data Center are not supported.
2. Contact support if Jira Data Center support is important for your evaluation.

Support

Need help? Contact us at support@supa-flow.io