Source connector

Jira connector

Jira integration for databases, warehouses and BI tools

Issue tracking for software and operations teams. Datrise captures Jira entities such as issues, sprints, projects, changelogs, and worklog events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Jira Cloud REST API v3 authenticates with OAuth 2.0, HTTP Basic, incremental runs key on updated (JQL clause, e.g. `updated >= -1d` or `updated >= "2026-09-01 00:00"`), and Jira caps calls at Tiered points-based quota enforced from March 2, 2026: default global pool 65,000 points/hour shared across tenants, or a per-tenant pool (Standard 100,000 + 10 pts/user/hour, Premium 130,000 + 20 pts/user/hour, Enterprise 150,000 + 30 pts/user/hour, capped at 500,000/hour), plus per-second burst caps (GET/POST 100 req/s, PUT/DELETE 50 req/s).

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `jira_issues`) with a schema derived from the Jira API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Jira pipeline page, and join the waitlist to get the Jira connector (Work management) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Jira data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
issues	jira_issues	Upsert by primary key, incremental on updated-at
sprints	jira_sprints	Upsert by primary key, incremental on updated-at
projects	jira_projects	Upsert by primary key, incremental on updated-at
changelogs	jira_changelogs	Upsert by primary key, incremental on updated-at
worklog events	jira_worklog_events	Append-only, incremental by timestamp

Jira API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Jira Cloud REST API v3
Authentication	OAuth 2.0, HTTP Basic — Server-to-server/script access uses HTTP Basic Auth with an email address plus an API token; Connect and OAuth apps use OAuth 2.0 (3LO) instead.
Pagination	token — `POST /rest/api/3/search/jql` uses token-based paging via `nextPageToken`; most other list endpoints still use the older `startAt`/`maxResults` offset style (default `maxResults` 50).
Rate limit	Tiered points-based quota enforced from March 2, 2026: default global pool 65,000 points/hour shared across tenants, or a per-tenant pool (Standard 100,000 + 10 pts/user/hour, Premium 130,000 + 20 pts/user/hour, Enterprise 150,000 + 30 pts/user/hour, capped at 500,000/hour), plus per-second burst caps (GET/POST 100 req/s, PUT/DELETE 50 req/s)
Incremental cursor	updated (JQL clause, e.g. `updated >= -1d` or `updated >= "2026-09-01 00:00"`) — JQL relative date filters like `-1d` only have day granularity; tight polling windows need an explicit `"yyyy-MM-dd HH:mm"` timestamp to avoid re-pulling a whole day of issues.
Webhooks	Yes — Jira Cloud Webhooks (issue created/updated/deleted, optionally scoped with a JQL filter)
Bulk export	No
Deletes detectable	Yes — Deleted issues disappear from JQL search results with no tombstone; detection requires either the `issue_deleted` webhook event or diffing the set of issue keys between two full ID-only searches.

Official API reference

What bites when replicating Jira

Atlassian began enforcing a new tiered points-based rate limit on March 2, 2026 (e.g. Standard edition: 100,000 points/hour + 10 points per licensed user), replacing looser historical throttling.
The classic `GET /rest/api/3/search` endpoint is deprecated in favor of `POST /rest/api/3/search/jql`, which switched from `startAt` offset paging to a `nextPageToken` cursor — code written against the old pagination breaks silently.
`maxResults` defaults to 50, and Atlassian explicitly documents that default/max page sizes 'may change without deprecation notice,' so hardcoding an assumed page size of 100 is not guaranteed to keep working.
There is no deleted-issue tombstone in the search API; the `issue_deleted` event only reaches you via a registered webhook, so a pure-polling integration cannot detect deletions at all.

Compare this against every other documented API

Popular destinations for Jira

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Jira connector FAQ

What Jira data does the connector extract?: 5 objects: issues, sprints, projects, changelogs and worklog events. Each lands in its own table with types preserved; history-style objects (1: worklog events) load as append-only streams.
Is the Jira integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Jira data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Jira → destination pair has its own page with the object-to-table mapping.

Related Work management sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Jira pipeline with guided onboarding

Join the waitlist to get priority access for Jira integrations with guided setup, schema-aware mapping, and production-grade incremental sync.