Jira connector
Set up the Jira connector in Kaivo: authentication, configuration, the 56 BigQuery tables it syncs, and answers to common questions.
Written By Lauri Raivio
Last updated 16 days ago
Kaivo is a fully managed data platform that syncs your Jira data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your project management data instead of moving it.
What is the Jira connector
Sync your Jira issues, boards, sprints, and worklogs into BigQuery with Kaivo to report on delivery and project progress without exporting spreadsheets.
Getting started with the Jira connector
- Sign up for Kaivo and create a workspace.
- Connect your Jira account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Jira
Authenticate with your API Token.
Configuring the Jira connector
When you set up the connector, you provide:
Tables and columns synced from Jira
Kaivo syncs 56 tables from Jira into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
application_roles (12 columns), Details of an application role.
application_roles (12 columns), Details of an application role.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
application_roles__groups(4 columns)application_roles__default_groups(4 columns)application_roles__group_details(3 columns)application_roles__default_groups_details(6 columns)
avatars (8 columns), List of system avatars.
avatars (8 columns), List of system avatars.
board_issues (13 columns)
board_issues (13 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
board_issues__fields__comment(3 columns)board_issues__fields__worklog(3 columns)
boards (17 columns)
boards (17 columns)
dashboards (22 columns), Details of a dashboard.
dashboards (22 columns), Details of a dashboard.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
dashboards__share_permissions(119 columns)dashboards__share_permissions__project__lead__groups__items(5 columns)dashboards__share_permissions__project__lead__application_roles__items(13 columns)dashboards__share_permissions__project__lead__application_roles__items__groups(4 columns)dashboards__share_permissions__project__lead__application_roles__items__default_groups(4 columns)dashboards__share_permissions__project__components(71 columns)dashboards__share_permissions__project__components__lead__groups__items(5 columns)dashboards__share_permissions__project__components__lead__application_roles__items(13 columns)dashboards__share_permissions__project__components__lead__application_roles__items__groups(4 columns)dashboards__share_permissions__project__components__lead__application_roles__items__default_groups(4 columns)dashboards__share_permissions__project__components__assignee__groups__items(5 columns)dashboards__share_permissions__project__components__assignee__application_roles__items(13 columns)dashboards__share_permissions__project__components__assignee__application_roles__items__groups(4 columns)dashboards__share_permissions__project__components__assignee__application_roles__items__default_groups(4 columns)dashboards__share_permissions__project__components__real_assignee__groups__items(5 columns)dashboards__share_permissions__project__components__real_assignee__application_roles__items(13 columns)dashboards__share_permissions__project__components__real_assignee__application_roles__items__groups(4 columns)dashboards__share_permissions__project__components__real_assignee__application_roles__items__default_groups(4 columns)dashboards__share_permissions__project__issue_types(27 columns)dashboards__share_permissions__project__versions(22 columns)dashboards__share_permissions__project__versions__operations(10 columns)dashboards__share_permissions__project__issue_type_hierarchy__level(11 columns)dashboards__share_permissions__project__issue_type_hierarchy__level__issue_type_ids(4 columns)dashboards__share_permissions__project__deleted_by__groups__items(5 columns)dashboards__share_permissions__project__deleted_by__application_roles__items(13 columns)dashboards__share_permissions__project__deleted_by__application_roles__items__groups(4 columns)dashboards__share_permissions__project__deleted_by__application_roles__items__default_groups(4 columns)dashboards__share_permissions__project__archived_by__groups__items(5 columns)dashboards__share_permissions__project__archived_by__application_roles__items(13 columns)dashboards__share_permissions__project__archived_by__application_roles__items__groups(4 columns)dashboards__share_permissions__project__archived_by__application_roles__items__default_groups(4 columns)dashboards__share_permissions__role__actors(11 columns)dashboards__editpermission(5 columns)dashboards__edit_permissions(3 columns)
filter_sharing (120 columns), Details of a share permission for the filter.
filter_sharing (120 columns), Details of a share permission for the filter.
filters (33 columns), Details of a filter.
filters (33 columns), Details of a filter.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
filters__owner__groups__items(5 columns)filters__owner__application_roles__items(13 columns)filters__owner__application_roles__items__groups(4 columns)filters__owner__application_roles__items__default_groups(4 columns)filters__share_permissions(120 columns)filters__share_permissions__project__lead__groups__items(5 columns)filters__share_permissions__project__lead__application_roles__items(13 columns)filters__share_permissions__project__lead__application_roles__items__groups(4 columns)filters__share_permissions__project__lead__application_roles__items__default_groups(4 columns)filters__share_permissions__project__components(71 columns)filters__share_permissions__project__components__lead__groups__items(5 columns)filters__share_permissions__project__components__lead__application_roles__items(13 columns)filters__share_permissions__project__components__lead__application_roles__items__groups(4 columns)filters__share_permissions__project__components__lead__application_roles__items__default_groups(4 columns)filters__share_permissions__project__components__assignee__groups__items(5 columns)filters__share_permissions__project__components__assignee__application_roles__items(13 columns)filters__share_permissions__project__components__assignee__application_roles__items__groups(4 columns)filters__share_permissions__project__components__assignee__application_roles__items__default_groups(4 columns)filters__share_permissions__project__components__real_assignee__groups__items(5 columns)filters__share_permissions__project__components__real_assignee__application_roles__items(13 columns)filters__share_permissions__project__components__real_assignee__application_roles__items__groups(4 columns)filters__share_permissions__project__components__real_assignee__application_roles__items__default_groups(4 columns)filters__share_permissions__project__issue_types(27 columns)filters__share_permissions__project__versions(22 columns)filters__share_permissions__project__versions__operations(10 columns)filters__share_permissions__project__issue_type_hierarchy__level(11 columns)filters__share_permissions__project__issue_type_hierarchy__level__issue_type_ids(4 columns)filters__share_permissions__project__deleted_by__groups__items(5 columns)filters__share_permissions__project__deleted_by__application_roles__items(13 columns)filters__share_permissions__project__deleted_by__application_roles__items__groups(4 columns)filters__share_permissions__project__deleted_by__application_roles__items__default_groups(4 columns)filters__share_permissions__project__archived_by__groups__items(5 columns)filters__share_permissions__project__archived_by__application_roles__items(13 columns)filters__share_permissions__project__archived_by__application_roles__items__groups(4 columns)filters__share_permissions__project__archived_by__application_roles__items__default_groups(4 columns)filters__share_permissions__role__actors(11 columns)filters__subscriptions(25 columns)filters__subscriptions__user__groups__items(5 columns)filters__subscriptions__user__application_roles__items(13 columns)filters__subscriptions__user__application_roles__items__groups(4 columns)filters__subscriptions__user__application_roles__items__default_groups(4 columns)
groups (4 columns), The list of groups found in a search, including header text (Showing X of Y matching groups) and total of matched groups.
groups (4 columns), The list of groups found in a search, including header text (Showing X of Y matching groups) and total of matched groups.
issue_changelogs (17 columns)
issue_changelogs (17 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_changelogs__items(10 columns)
issue_comments (12 columns), A comment.
issue_comments (12 columns), A comment.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_comments__properties(4 columns)
issue_custom_field_contexts (9 columns), The details of a custom field context.
issue_custom_field_contexts (9 columns), The details of a custom field context.
issue_custom_field_options (8 columns), Details of the custom field options for a context.
issue_custom_field_options (8 columns), Details of the custom field options for a context.
issue_field_configurations (6 columns), Details of a field configuration.
issue_field_configurations (6 columns), Details of a field configuration.
issue_fields (30 columns), Details about a field.
issue_fields (30 columns), Details about a field.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_fields__clause_names(4 columns)
issue_link_types (7 columns), A list of issue link type beans.
issue_link_types (7 columns), A list of issue link type beans.
issue_navigator_settings (4 columns), Details of an issue navigator column item.
issue_navigator_settings (4 columns), Details of an issue navigator column item.
issue_notification_schemes (22 columns), Details about a notification scheme.
issue_notification_schemes (22 columns), Details about a notification scheme.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_notification_schemes__notification_scheme_events(6 columns)issue_notification_schemes__notification_scheme_events__notifications(74 columns)issue_notification_schemes__notification_scheme_events__notifications__field__clause_names(4 columns)issue_notification_schemes__notification_scheme_events__notifications__project_role__actors(11 columns)
issue_priorities (9 columns), An issue priority.
issue_priorities (9 columns), An issue priority.
issue_properties (6 columns), An entity property, for more information see [Entity properties](https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/).
issue_properties (6 columns), An entity property, for more information see [Entity properties](https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/).
issue_remote_links (19 columns), Details of an issue remote link.
issue_remote_links (19 columns), Details of an issue remote link.
issue_resolutions (7 columns), Details of an issue resolution.
issue_resolutions (7 columns), Details of an issue resolution.
issue_security_schemes (7 columns), List of security schemes.
issue_security_schemes (7 columns), List of security schemes.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_security_schemes__levels(7 columns)
issue_transitions (22 columns)
issue_transitions (22 columns)
issue_type_schemes (7 columns), Details of an issue type scheme.
issue_type_schemes (7 columns), Details of an issue type scheme.
issue_type_screen_schemes (5 columns), Details of an issue type screen scheme.
issue_type_screen_schemes (5 columns), Details of an issue type screen scheme.
issue_types (27 columns), Details about an issue type.
issue_types (27 columns), Details about an issue type.
issue_votes (6 columns), The details of votes on an issue.
issue_votes (6 columns), The details of votes on an issue.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_votes__voters(22 columns)issue_votes__voters__groups__items(5 columns)issue_votes__voters__application_roles__items(13 columns)issue_votes__voters__application_roles__items__groups(4 columns)issue_votes__voters__application_roles__items__default_groups(4 columns)
issue_watchers (6 columns), The details of watchers on an issue.
issue_watchers (6 columns), The details of watchers on an issue.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_watchers__watchers(16 columns)
issue_worklogs (38 columns), Details of a worklog.
issue_worklogs (38 columns), Details of a worklog.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issue_worklogs__properties(5 columns)
issues (167 columns)
issues (167 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
issues__rendered_fields__labels(4 columns)issues__rendered_fields__issuelinks(4 columns)issues__rendered_fields__components(3 columns)issues__rendered_fields__attachment(4 columns)issues__rendered_fields__subtasks(4 columns)issues__rendered_fields__comment__comments(32 columns)issues__rendered_fields__comment__comments__body__content(4 columns)issues__rendered_fields__comment__comments__body__content__content(5 columns)issues__rendered_fields__worklog__worklogs(4 columns)issues__transitions(21 columns)issues__changelog__histories(16 columns)issues__changelog__histories__items(12 columns)issues__fields__attachment(4 columns)issues__fields__comment__comments(4 columns)issues__fields__components(4 columns)issues__fields__description__content(4 columns)issues__fields__description__content__content(5 columns)issues__fields__fix_versions(4 columns)issues__fields__issuelinks(4 columns)issues__fields__labels(4 columns)issues__fields__subtasks(4 columns)issues__fields__versions(4 columns)issues__fields__worklog__worklogs(35 columns)issues__fields__worklog__worklogs__comment__content(4 columns)issues__fields__worklog__worklogs__comment__content__content(5 columns)
jira_settings (10 columns), Details of an application property.
jira_settings (10 columns), Details of an application property.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
jira_settings__allowed_values(4 columns)
labels (3 columns)
labels (3 columns)
permission_schemes (22 columns), List of all permission schemes.
permission_schemes (22 columns), List of all permission schemes.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
permission_schemes__permissions(10 columns)
permissions (6 columns), Details about permissions.
permissions (6 columns), Details about permissions.
project_avatars (9 columns), List of project avatars.
project_avatars (9 columns), List of project avatars.
project_categories (6 columns), A project category.
project_categories (6 columns), A project category.
project_components (52 columns), Details about a project component.
project_components (52 columns), Details about a project component.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
project_components__lead__groups__items(5 columns)project_components__lead__application_roles__items(13 columns)project_components__lead__application_roles__items__groups(4 columns)project_components__lead__application_roles__items__default_groups(4 columns)project_components__assignee__groups__items(5 columns)project_components__assignee__application_roles__items(13 columns)project_components__assignee__application_roles__items__groups(4 columns)project_components__assignee__application_roles__items__default_groups(4 columns)
project_email (4 columns), A project's sender email address.
project_email (4 columns), A project's sender email address.
project_permission_schemes (7 columns), Details about a security scheme.
project_permission_schemes (7 columns), Details about a security scheme.
project_roles (26 columns), Project Roles
project_roles (26 columns), Project Roles
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
project_roles__actors(12 columns)
project_types (7 columns), Details about a project type.
project_types (7 columns), Details about a project type.
project_versions (21 columns)
project_versions (21 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
project_versions__operations(10 columns)
projects (31 columns), Details about a project.
projects (31 columns), Details about a project.
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
projects__components(4 columns)projects__issue_types(4 columns)projects__versions(4 columns)
screen_schemes (9 columns), A screen scheme.
screen_schemes (9 columns), A screen scheme.
screen_tab_fields (6 columns), A screen tab field.
screen_tab_fields (6 columns), A screen tab field.
screen_tabs (5 columns), A screen tab.
screen_tabs (5 columns), A screen tab.
screens (20 columns)
screens (20 columns)
sprint_issues (24 columns)
sprint_issues (24 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
sprint_issues__fields__comment(3 columns)sprint_issues__fields__worklog(3 columns)
sprints (13 columns)
sprints (13 columns)
time_tracking (5 columns), Details about the time tracking provider.
time_tracking (5 columns), Details about the time tracking provider.
users (21 columns), A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: * User record deleted from Atlassian: This occurs as the result of a right to be forgotten request. In this case, `displayName` provides an indication and other parameters have default values or are blank (for example, email is blank). * User record corrupted: This occurs as a results of events such as a server import and can only happen to deleted users. In this case, `accountId` returns *unknown* and all other parameters have fallback values. * User record unavailable: This usually occurs due to an internal service outage. In this case, all parameters have fallback values.
users (21 columns), A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: * User record deleted from Atlassian: This occurs as the result of a right to be forgotten request. In this case, `displayName` provides an indication and other parameters have default values or are blank (for example, email is blank). * User record corrupted: This occurs as a results of events such as a server import and can only happen to deleted users. In this case, `accountId` returns *unknown* and all other parameters have fallback values. * User record unavailable: This usually occurs due to an internal service outage. In this case, all parameters have fallback values.
users_groups_detailed (21 columns), A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: * User record deleted from Atlassian: This occurs as the result of a right to be forgotten request. In this case, `displayName` provides an indication and other parameters have default values or are blank (for example, email is blank). * User record corrupted: This occurs as a results of events such as a server import and can only happen to deleted users. In this case, `accountId` returns *unknown* and all other parameters have fallback values. * User record unavailable: This usually occurs due to an internal service outage. In this case, all parameters have fallback values.
users_groups_detailed (21 columns), A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: * User record deleted from Atlassian: This occurs as the result of a right to be forgotten request. In this case, `displayName` provides an indication and other parameters have default values or are blank (for example, email is blank). * User record corrupted: This occurs as a results of events such as a server import and can only happen to deleted users. In this case, `accountId` returns *unknown* and all other parameters have fallback values. * User record unavailable: This usually occurs due to an internal service outage. In this case, all parameters have fallback values.
workflow_schemes (30 columns)
workflow_schemes (30 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
workflow_schemes__last_modified_user__groups__items(5 columns)workflow_schemes__last_modified_user__application_roles__items(13 columns)workflow_schemes__last_modified_user__application_roles__items__groups(4 columns)workflow_schemes__last_modified_user__application_roles__items__default_groups(4 columns)
workflow_status_categories (7 columns), A status category.
workflow_status_categories (7 columns), A status category.
workflow_statuses (13 columns), A status.
workflow_statuses (13 columns), A status.
workflows (9 columns)
workflows (9 columns)
Nested subtables
Repeating fields are split into their own tables, listed here with their column counts.
workflows__transitions(9 columns)workflows__transitions__from(4 columns)workflows__transitions__rules__conditions(5 columns)workflows__transitions__rules__validators(5 columns)workflows__transitions__rules__post_functions(5 columns)workflows__statuses(6 columns)
How the Jira sync works
After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Jira supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.
Frequently asked questions
How long does the initial sync take for Jira?
It depends on how much history is in your Jira account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.
Can I sync only some tables or columns?
Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.
What happens when Jira's schema changes?
New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in Jira, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Jira instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Jira connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Jira data
Sprint velocity
Combine issues with sprints and boards to measure velocity, scope changes, and completion rates across teams and over time.
Cycle and lead time
Use issue created, updated, and resolution dates to estimate cycle and lead time and spot where work stalls in the workflow.
Backlog and throughput
Track issues by status, priority, and issue type to monitor backlog growth, throughput, and the mix of work being delivered.
Time reporting
Aggregate worklogs by user, project, and issue to report logged time and how effort is distributed across initiatives.
Cross-tool delivery reporting
Join Jira issues with data from your other tools in BigQuery to build delivery dashboards that span product, support, and engineering.
Use Jira data in your AI and BI tools
Once Jira data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with Jira data.
Claude
Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Excel
Connect via Power Query's BigQuery connector. Setup guide →
Metabase
Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Jira connector pricing and plan details.
Related connectors
Was this helpful?
Still need help? Share an idea