Jira to BigQuery, answered.

Everything people ask about getting Jira Cloud data into Google BigQuery — and how BigQuery Sync for Jira by FreeMetrics handles it.

Getting Jira data into BigQuery

How do I get Jira data into BigQuery?

Install BigQuery Sync for Jira from the Atlassian Marketplace, paste a Google service-account key, choose your projects, and press Start sync. The plugin creates 16 tables and 11 analytics views in your own BigQuery dataset and keeps them current — no scripts, no middleware, no servers of your own. Setup takes about ten minutes; see the setup guide.

Is there a Jira BigQuery connector on the Atlassian Marketplace?

Yes. BigQuery Sync for Jira runs entirely inside Atlassian Forge, so Jira data flows directly from Atlassian to your Google Cloud project — there are no vendor servers in between. It syncs issues, changelog, comments, worklogs, sprints, boards and all reference data.

How do I sync Jira to Google Cloud (GCP)?

BigQuery is the natural landing place for Jira data on Google Cloud. The connector writes to any BigQuery dataset and location you choose using free load jobs; from there the data is available to Looker Studio, Vertex AI, Dataform, or anything else on GCP.

Can I export Jira issues to BigQuery automatically?

Yes — changes sync every 5 minutes by default, with an hourly reference-data refresh and a nightly full reconcile that catches anything missed. You can also trigger any job manually.

Do I need an ETL tool like Fivetran or Airbyte to load Jira into BigQuery?

No. A general-purpose ETL platform needs its own infrastructure or SaaS contract, charges by rows, and treats Jira as one of hundreds of sources. A native Forge connector is purpose-built: it understands sprints, changelogs, custom fields and deletions, is billed simply per Jira user through your Atlassian invoice, and never routes your data through third-party servers.

Can I use the Jira REST API to load data into BigQuery myself?

You can — but you will need to handle pagination, rate limits, changelog fetching, worklog deletions, custom-field mapping, schema evolution and nightly reconciliation, then keep that pipeline running. The connector is that pipeline, maintained for you and reviewed by Atlassian.

How long does the first backfill take?

A site with 50,000 issues typically finishes within an hour. Backfills resume where they stopped and respect Jira's rate limits, so sites with hundreds of thousands of issues complete safely.

Analytics and BI tools

How do I connect Jira to Looker Studio?

Sync Jira to BigQuery with the connector, then add a BigQuery data source in Looker Studio and pick views like issues_current or sprint_report. No SQL needed — the views are ready-made data sources.

How do I build Jira dashboards in Power BI or Tableau?

Both connect natively to BigQuery. Point them at your synced dataset and use the included views — time_in_status, issue_cycle_times, throughput_weekly, assignee_workload and more — as drag-and-drop sources.

Can I query Jira with SQL?

Yes — that is the point. Once synced, every issue, comment, worklog and field change is a BigQuery row. SELECT COUNT(*) FROM issues_current WHERE status_category = 'In Progress' just works.

How do I calculate time in status in Jira?

The connector ships a time_in_status view built from the full changelog: total time per issue per status, ready to chart. A companion status_transitions view powers cumulative-flow and bottleneck analysis.

How do I get sprint reports outside Jira?

The sprint_report view gives committed, completed, added, removed and carried-over per sprint — the numbers from Jira's sprint report, as queryable rows for any BI tool.

How do I export the Jira changelog or issue history?

The changelog table records every field change with author and timestamp. Tables are append-only, so you can also query the dataset as it looked on any past date — useful for trend lines Jira itself cannot show.

Can I keep Jira history for trend analysis?

Yes. Nothing is overwritten: every sync appends, *_current views expose the latest state, and a nightly snapshot table records every open issue per day — so "how many open bugs did we have on 1 March" is one query.

Coverage

Does it export Jira custom fields?

Every custom field becomes a typed column automatically, including team-managed story points and sprints. Add a field in Jira and it appears in BigQuery on the next run.

Does it support Jira Service Management?

Issues, comments and worklogs from JSM projects sync like any other project. Request types, SLAs and queues are on the roadmap.

What about deleted issues — will my numbers match Jira?

Deletions of issues, comments and worklogs are captured as tombstone rows and excluded from the _current views, so totals in BigQuery match totals in Jira.

Can I sync multiple Jira projects to different datasets?

Yes — up to ten syncs per site, each with its own projects, JQL filter, dataset, schedule and optionally its own service-account key.

Security, permissions and cost

Is my Jira data safe — where does it flow?

The app runs on Atlassian Forge and talks only to bigquery.googleapis.com and oauth2.googleapis.com — your own Google project, declared in the manifest and reviewed by Atlassian. FreeMetrics has no servers that could see your data, and your service-account key is stored in Atlassian's encrypted secret storage. Details in the privacy policy.

Which Google Cloud permissions are needed?

Two roles on a dedicated service account: BigQuery Job User on the project and BigQuery Data Editor on one dataset. Nothing else in your project is touched. The docs include a copy-paste gcloud script.

How much does a Jira BigQuery connector cost?

Free for sites with up to 10 Jira users — forever, with every feature. Larger sites pay per user at a rate that decreases with size; the exact price for your user count is shown on the Atlassian Marketplace listing before you subscribe. BigQuery's own cost is small: load jobs are free and a 100,000-issue site stores well under 1 GB. See pricing.

Is there a free way to get Jira data into BigQuery?

For small teams, yes — the connector is free forever for sites with 10 users or fewer, with every feature included. Larger sites get a 30-day free trial.

What is the easiest way to build a Jira data warehouse?

Install the connector, and ten minutes later you have one: complete raw tables, append-only history, analytics views maintained for you, and a dbt package if you prefer to own the models in your repo. Anything missing for your use case — tell us and we build it.