Search
Search Jira records by query.
- Source
- Engineering Analytics
- Generally available
- 9 entities
- Read & write
Move Jira data anywhere it matters.
Send Jira application roles, avatars and boards to any warehouse, lake or AI app.
Source
Jira
Snowflake
BigQuery
Postgres
Databricks
Claude
- Streams
- 55
- Entities
- 9
- Actions
- 8
- Destinations
- 50+
- Certified support
- 6.1.0
Overview
What is the Airbyte Jira connector?
The Airbyte Jira connector extracts data from Jira and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes 55 streams you can select per connection.
- 01
Sync to your warehouse
Land 55 Jira tables in 50+ destinations on a schedule you control.
- 02
Live entity actions
Read, create, update and delete Jira records at runtime through typed entity actions.
- 03
Context store search
Query synced Jira data with filters, sorting and semantic search, without spending Jira API rate limits.
- 04
Incremental syncs
Pull only the records that changed since the last run instead of reloading everything.
55 streams
Every table you can sync from Jira
Application roles Sync modes FullIncr. Avatars Sync modes FullIncr. Boards Sync modes FullIncr. Dashboards Sync modes FullIncr. Filters Sync modes FullIncr. Filter sharing Sync modes FullIncr.
Setup
Live in ten steps
First, navigate to the Airbyte dashboard and click on "Sources" on the left-hand side of the screen.
Click on the "Add Source" button in the top right corner of the screen.
Select "Jira" from the list of available sources.
Enter a name for your Jira source connector and click "Next".
Enter your Jira credentials, including the Jira URL, email address, and API token.
Test the connection to ensure that the credentials are correct and the connection is successful.
Select the Jira projects and issue types that you want to replicate in Airbyte.
Choose the replication frequency and any other settings that you want to apply to your Jira source connector.
Click "Create Source" to save your Jira source connector and begin replicating data from Jira to Airbyte.
It is important to note that the specific steps for connecting your Jira source connector may vary depending on your specific use case and the version of Jira that you are using. For more detailed instructions and troubleshooting tips, refer to the Airbyte documentation or consult with a Jira expert.
Configuration fields
| Field | Type | Description |
|---|---|---|
| credentials* | object | Choose how to authenticate to Jira. |
| domain* | string | Your Jira host (full domain — do not include 'https://' or paths). Examples: airbyteio.atlassian.net, airbyteio.jira.com, jira.your-domain.com. |
| expand_issue_changelog | boolean | (DEPRECATED) Expand the changelog when replicating issues. |
| expand_issue_transition | boolean | (DEPRECATED) Expand the transitions when replicating issues. |
| issues_stream_expand_with | array | Select fields to Expand the Issues stream when replicating with: |
| lookback_window_minutes | integer | When set to N, incremental syncs of issues, board_issues and sprint_issues start N minutes before the last synced updated value, so changes Jira had not indexed yet are picked up. Records in that window are emitted again. |
| num_workers | integer | The number of worker threads to use for the sync. |
| projects | array | List of Jira project keys to replicate data for, or leave it empty if you want to replicate data for all projects. |
8 actions
Supported Jira actions
Create
Writea new record back into Jira.Get
Fetcha single record by ID.Update
Patchfields on an existing record.Delete
Removea record.Context Store Search
Query synced data with filters and sorting, with no API rate limits.
Semantic Search
Natural-language search across synced Jira records.
List
Readlive records straight from the Jira API.
Full parameter-level details live in the Jira entity reference.
Hybrid deployment
Sovereign by architecture, not by policy.
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
- Cloud
- OSS
- Hybrid
Your environment
Airbyte control plane
Use cases
What teams build with Jira
Show me all open issues in my Jira instance
List recent issues created in the last 7 days
Show me details for the most recently updated issue
List all projects in my Jira instance
Show me the details of the first project
List all users in my Jira instance
Show me the details of the first user
Search for a user by name in my Jira instance
Show me comments on the most recent issue
Show me the details of the first comment on the most recent issue
Show me worklogs from the last 7 days
Show me the details of the first worklog on the most recent issue
List all issue fields in my Jira instance
Search for issue fields related to priority
What transitions are available for the most recent issue?
Assign a recent issue to a teammate
Unassign a recent issue
Create a new task called 'Sample task' in a project
Create a bug with high priority
Update the summary of a recent issue to 'Updated summary'
Change the priority of a recent issue to high
Add a comment to a recent issue saying 'Please investigate'
Update my most recent comment
Delete a test issue
Remove my most recent comment
Transition the most recent issue to In Progress
Move the most recent issue to Done
Log 2 hours of work on the most recent issue
Link the most recent issue as blocking the next most recent issue
Create a 'relates to' link between my two most recent issues
What issues are assigned to team_member this week?
Find all high priority bugs in our current sprint
Show me overdue issues across all projects
What projects have the most issues?
Search for users named user_name
FAQ
Jira connector questions
Do I need more than one Jira connection?
No. One Jira authorization powers both the scheduled syncs that land data in your destination and the entity actions your agents call at runtime.
Do Jira entity actions need a sync to run first?
No. Entity actions read and write through the Jira API as they are called, so they work immediately. Context store search is the exception: it queries data Airbyte has already synced, which is what lets it filter and sort without spending API rate limits.
What data can I sync from Jira with Airbyte?
55 streams, including Application roles, Avatars, Boards, Dashboards, Filters, Filter sharing, Groups, Issue fields and more.
Does the Jira connector support incremental sync?
Yes. The Jira connector supports incremental sync on selected streams, and full refresh on every stream.
Where can I run the Jira connector?
Run the Jira connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Start syncing Jira in minutes.
Free 14-day trial. One connection powers your scheduled syncs and your live Jira actions.