How to Connect Jira to Google Sheets

Jira exports issues to CSV in about two minutes, and for a small one-off that is the right answer. The reason people end up looking for something else is the 1,000-issue cap on that export, and the fact that it never updates. This guide covers the CSV route and where it stops, the free REST API method that handles any issue count with JQL, and the two details that break most first attempts: unreadable custom field IDs and the search endpoint Atlassian recently replaced.

The two-minute option: CSV export

In Jira, open Filters → View all issues, build the filter you want (JQL works here), then use the export menu and choose Export Excel CSV. Import the file into Sheets via File → Import.

Two limits arrive quickly. The export is capped at 1,000 issues, which a single active project passes in a quarter, and the "all fields" variant produces a very wide sheet with every custom field your instance has ever defined. Pick "current fields" and configure the columns you want in the navigator first.

Jira to Google Sheets for free (Apps Script + REST API)

Create an API token at id.atlassian.com → Security → API tokens. Jira Cloud authenticates with your account email and that token, combined as basic auth. Your site URL is the your-domain.atlassian.net host.

Two things to know before the code. First, Atlassian replaced /rest/api/3/search with /rest/api/3/search/jql on Jira Cloud. The new endpoint pages with an opaque nextPageToken rather than startAt offsets, and it deliberately does not return a total count, so any code that loops until startAt > total needs rewriting. Second, always pass an explicit fields list. Requesting everything on a large result set is dramatically slower and can time out.

1function importJiraIssues() {2  const SITE  = "your-domain.atlassian.net";3  const EMAIL = "[email protected]";4  const TOKEN = "YOUR_API_TOKEN";5  const JQL   = 'project = ENG AND updated >= -30d ORDER BY created DESC';6 7  const auth = "Basic " + Utilities.base64Encode(EMAIL + ":" + TOKEN);8  const headers = { Authorization: auth, Accept: "application/json" };9 10  // Custom fields come back as customfield_NNNNN. Fetch the mapping so the11  // header row says "Story Points" rather than "customfield_10016".12  const fieldNames = {};13  JSON.parse(14    UrlFetchApp.fetch("https://" + SITE + "/rest/api/3/field", { headers })15      .getContentText()16  ).forEach((f) => { fieldNames[f.id] = f.name; });17 18  const WANTED = ["summary", "status", "assignee", "priority",19                  "created", "resolutiondate", "customfield_10016"];20 21  const rows = [];22  let nextPageToken = null;23 24  do {25    let url = "https://" + SITE + "/rest/api/3/search/jql"26      + "?jql=" + encodeURIComponent(JQL)27      + "&maxResults=100"28      + "&fields=" + WANTED.join(",");29    if (nextPageToken) url += "&nextPageToken=" + nextPageToken;30 31    const page = JSON.parse(32      UrlFetchApp.fetch(url, { headers }).getContentText()33    );34 35    (page.issues || []).forEach((issue) => {36      const f = issue.fields;37      rows.push([38        issue.key,39        f.summary || "",40        f.status ? f.status.name : "",41        f.assignee ? f.assignee.displayName : "Unassigned",42        f.priority ? f.priority.name : "",43        f.created || "",44        f.resolutiondate || "",45        f.customfield_10016 || "",46      ]);47    });48 49    // No "total" is returned. Stop when Jira stops handing back a token.50    nextPageToken = page.nextPageToken || null;51  } while (nextPageToken);52 53  const header = ["Key", ...WANTED.map((id) => fieldNames[id] || id)];54  const ss = SpreadsheetApp.getActiveSpreadsheet();55  const sheet = ss.getSheetByName("Jira") || ss.insertSheet("Jira");56  sheet.clearContents();57  sheet.getRange(1, 1, 1, header.length).setValues([header]);58  if (rows.length) {59    sheet.getRange(2, 1, rows.length, header.length).setValues(rows);60  }61}

Run once to authorise, then add a time-driven trigger under Triggers → Add Trigger → Time-driven. Note that nearly every interesting Jira field is an object rather than a string: status, assignee, priority and resolution all need a property picked off them, which is why the code above reads .name and .displayName rather than writing the field directly.

Limits: Apps Script stops at six minutes, so very large JQL results need splitting by date range across runs. Custom field IDs differ per Jira site, so this script is not portable between instances without re-checking them. There is no write-back unless you build it.

Jira Server and Data Center

Self-hosted instances differ in two ways. The path is /rest/api/2/ rather than /rest/api/3/, and authentication uses a personal access token sent as Authorization: Bearer <token>, created from your profile under Personal Access Tokens. Older versions still accept basic auth with a password. The classic startAt and maxResults pagination remains in place on these versions, so the offset loop older tutorials show is correct here even though it is not on Cloud.

The Brooked method

Brooked runs your JQL against the API, pages through the whole result set, resolves custom field IDs to their display names, and flattens the nested status and user objects into plain columns. Cloud, Server and Data Center are all supported, and several projects can land in one spreadsheet on a single schedule.

Step 1: Install Brooked

Install Brooked from the Google Workspace Marketplace. Free tier includes 100 imports per month, no credit card required.

Step 2: Connect Jira and write your JQL

Choose Jira in Brooked, enter your site URL, account email and API token. Then either pick a saved filter or paste JQL directly. Anything valid in the issue navigator is valid here, so project = ENG AND status changed to Done during (-14d, now()) works as written.

Step 3: Schedule the refresh

Set the import to re-run hourly, daily or weekly so sprint reports and dashboards rebuild themselves. Relative JQL dates like -30d re-evaluate on each run, so a rolling window stays rolling without anyone editing the query.

Brooked AI, Jira

Live

Ask anything about your Jira data…

Method comparison

Common use cases

• Sprint reporting: rebuild velocity and burndown tables that leadership reads in Sheets, not Jira
• Cycle time analysis: compare created against resolutiondate to measure how long work actually takes
• Cross-project roll-ups: report across several projects in one table, which Jira dashboards make awkward
• Bug triage: track open defects by component, priority and age with your own scoring columns
• Capacity planning: join story points against a team roster that already lives in the spreadsheet

Troubleshooting common issues

Related Articles

• How to Connect Monday.com to Google Sheets
• How to Connect Clockify to Google Sheets
• How to Connect ClickUp to Google Sheets

Frequently asked questions