Skip to content

Connect Google Sheets to Jira

Spreadsheets are where requests, new hires and checklists often start, and Jira is where the work gets tracked. Connecting Google Sheets and Jira turns rows into tickets with the key written back, and keeps a sheet of Jira reports that anyone in the company can read.

Build your own

Build any Google Sheets and Jira automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Google Sheets and Jira in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, write all open Jira bugs older than 14 days to a sheet tab, with a column where AI suggests whether each looks stale.

When the Priority column in my backlog sheet changes, update the matching Jira issue's priority, but only for rows with a Jira key.

Use cases

Why people connect Google Sheets and Jira

How the two apps work together

  • On a schedule, the script runs a JQL query and writes or updates rows in a Google Sheets tab.
  • The script checks the sheet every few minutes for new or changed rows and creates or updates Jira issues.
  • Jira webhooks can also send issue events to a trigger link so rows update as tickets change.
  • Jira reports for people without Jira

    Operations and finance teams get a sheet of tickets with key, status, assignee and story points. They build pivot tables and charts without Jira access.

  • Bulk ticket creation from planning

    Project managers plan a release in a sheet and turn rows marked ready into Jira issues. The issue key is written back into the row.

  • Time and capacity tracking

    Delivery leads log logged hours and story points per person each week. The sheet shows capacity against what was planned.

  • Intake form for requests

    Teams collect requests through a Google Form into a sheet, and each new row becomes a Jira task in the right project.

More apps

Google Sheets, Jira and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Form requests to Jira via a sheet

When a new Google Forms response lands in my Requests sheet, create a Jira task in project OPS and write the key in column F.

Weekly Jira report sheet and Slack summary

Every Friday, refresh my Jira Report sheet with this week's resolved tickets and post the count per assignee in #team.

Release checklist across Jira and GitHub

Keep a sheet of tickets in the current fix version with their Jira status and whether a linked GitHub PR is merged.

Setup

Connect Google Sheets and Jira once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Google Sheets

Spreadsheets

  1. In the ClickRuntime dashboard, open Connections and choose Google Sheets.
  2. Sign in with your Google account and allow access.
  3. Pick the spreadsheets the automation may use. It can't see any other file in your Drive.

Jira

Project management / Issue tracking

  1. Go to id.atlassian.com/manage-profile/security/api-tokens and choose Create API token. Atlassian sends a code to your email to confirm.
  2. Name the token, choose an expiry of 1 to 365 days, create it and copy it straight away. It can't be shown again.
  3. Note your site address, such as yoursite.atlassian.net, and the email of the Atlassian account that created the token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the email, token and site for Jira.

FAQ

Questions about connecting Google Sheets and Jira

Will it create a ticket twice for the same row?
No. Once a ticket is created, its key is written back into the row, and rows with a key are skipped.
Can people without Jira add requests?
Yes. Anyone who can edit the sheet, or fill in a Google Form that feeds it, can add a row. The ticket is created by your connected Jira account.
Which Google account does it use?
The Google account you connect in your ClickRuntime dashboard. Share the sheet with it as an editor.
Can I add my own columns?
Yes. Add columns to the right of the ones the automation uses. They are left alone.
Can it handle large Jira projects?
Yes. The script pages through JQL results, so it can write thousands of tickets. Very large sheets are slower to update, so many people keep one tab per project or period.
Does it overwrite the whole sheet each time?
Only if you ask for that. It can also update rows by ticket key and append new ones, leaving your own columns alone.
Can sheet edits change Jira tickets?
Yes. The script checks the sheet on a schedule and updates the fields you choose, such as status, priority or assignee.

Tell your assistant what Google Sheets and Jira should do together

Free plan. No credit card.