Jira and Google Sheets, ready to switch on

Every issue matching the filter you name has a row that changes as the issue moves, sprint and story points sit in their own columns, and a line on the requests tab becomes an issue with its key written beside it. You paste two keys in your account and it runs, in about ten minutes.

No setup fee, cancel any month, and a person on live chat if a key doesn't work.

More with these apps: all Jira integrations · all Google Sheets integrations

Atlassian has an official Jira add-on for Sheets.

It has: Atlassian's help describes Jira Cloud for Sheets, which imports issues from a saved filter or a JQL query into a spreadsheet. If a refresh now and then is enough, install the add-on. This pair keeps the rows current without anybody opening the sheet, and lets a requests tab create issues. Nothing to install in Sheets or Jira.

What moves, and when

The details you would normally get after a sales call. Here they are up front.

WhatDirectionWhenRule
Filter results as rowsJira to Google SheetsWithin secondsEvery issue matching the JQL you name, one row each: key, summary, type, status, assignee, priority, created, updated
Status changes edit the cellJira to Google SheetsWithin secondsThe status and updated cells change on that issue's row; nothing is appended below
Sprint and story pointsJira to Google SheetsWhen they changeIn their own columns, which is what makes a burndown chart possible in a sheet
Requests tab opens issuesGoogle Sheets to JiraEvery few minutesA line with a summary on the Requests tab becomes an issue in the project you name, and the key is written beside it
Resolved rows stay putIn the sheetAlwaysResolved issues keep their row and their status, so the sheet is also the history
Formulas to the right surviveIn the sheetAlwaysAnything you add beyond our columns is left alone

How to set up Jira and Google Sheets

Ten minutes of your time, then it's ours.

  1. Choose Jira and Google Sheets
    Press Connect. This pair is already selected on the checkout page at $39 a month, and there's nothing else to pick.
  2. Pay and open your account
    Card or invoice, about two minutes. The account opens with this integration waiting for its two keys.
  3. Paste the Jira Cloud API token and the Google Sheets link
    • Jira Cloud API token: open id.atlassian.com/manage-profile/security/api-tokens and press Create API token. Full Jira guide
    • Google Sheets link: create or open the spreadsheet, share it with the address our engineer sends you or with anyone who has the link, and paste the link from the address bar. Full Google Sheets guide
    Each screen carries the full guide with the exact menu names, about five minutes for both.
  4. We check both keys
    Each key is checked against Jira's and Google Sheets's own API the moment you paste it. If one doesn't pass, the screen says what to fix, and a person joins the chat if that isn't enough.
  5. Add one test row, then it's Running
    A minute or two. Add a row in Google Sheets and wait for the issue to appear in Jira. It runs on a short schedule, so give it a minute.

When Jira or Google Sheets changes its API, we fix it within a working day. You don't get a ticket to solve.

$39a month
  • Everything in the table above, with monitoring on.
  • Fixes when either app changes its API.
  • A person on live chat, replies within a working hour.
  • Custom logic beyond the table is priced separately.
Connect for $39 a month

No setup fee, cancel any month

Ways to connect Jira and Google Sheets

Three ways people connect these two, and what each one asks of you. The built-in app is described above.

Built-in appZapier or MakeDovetly
Who sets it upYou, in the app's own settingsYou, one step at a time in the scenario editorAlready built. You paste two keys.
Who fixes it when it breaksThe vendor, when it ships a fixYou: the scenario is yours, so the fix is tooWe do, within a working day, and we watch it
What you need to knowThe app's own settings and what they coverTriggers, actions, filters and how the fields of Jira and Google Sheets mapWhere the two keys are. The guide shows it.
PriceSet by the vendorSet by the builder's plan, counted in tasks or operations$39 a month, flat, whatever the volume

Before you decide

Can several filters go to several tabs?

Yes. One JQL per tab, so a support queue and a sprint can live in the same file without mixing. Each tab keeps its own columns.

Does Jira integrate with Google Sheets?

Yes. Every issue matching the JQL you name has a row that changes as the issue moves, sprint and story points sit in their own columns, and a line on the requests tab becomes an issue with its key written beside it. Atlassian's own add-on imports when you refresh (above); this pair keeps the rows current on its own. $39 a month.

Can you use Google Sheets as an API?

For this pair the sheet is the interface, and you never touch an API. You share the spreadsheet with the address we give you and paste the link with a Jira Cloud API token. Rows follow the issues, and anything you type on the requests tab becomes an issue within a few minutes.

What if mine is a bit different?

Tell us what should go where in plain words. Small changes to the rules above are usually free; bigger ones we price the same day and build into the same account.