The Google Sheets Jira integration most teams use is Atlassian's free Jira Cloud for Sheets add-on. It pulls Jira tickets into a sheet from a filter or a JQL search, and Jira's search page has an Open in Google Sheets button that does the same. To go the other way, from a sheet into Jira, you save the sheet as a CSV file and load it with Jira's CSV importer, or build a Zapier zap. Where it stops: the add-on only reads from Jira, recent reviews say it stops loading, the importer is a one-time upload, and nobody chases the tickets the sheet shows are late. AI agents do that follow-up.
What a Google Sheets Jira integration has to do
Jira holds the work. The sheet is where a manager, a client or the owner looks at it: a weekly status, a list of requests, a budget of hours. When the two drift apart, someone pastes tickets into the sheet by hand before each meeting, and someone else types sheet rows into Jira one at a time.
So a Google Sheets Jira integration has to do two things. Tickets have to show up in the sheet, current, without a person copying them. And new rows in the sheet, like requests from a client, have to become tickets without being typed twice. Atlassian's own options do the first. The second takes an upload or a zap.
Three ways to connect Jira and Google Sheets
Most teams start with the add-on to read Jira, and add one of the others if rows need to go into Jira.
Jira Cloud for Sheets
- How it works
- Atlassian's free add-on from the Google Workspace Marketplace. You connect your Jira Cloud site, then use Get data from Jira to pull tickets in from a starred filter or a JQL search. A =JIRA() formula runs a search right from a cell. Jira's search page also has an Open in Google Sheets button.
- Good for
- Managers who want a sheet of Jira tickets for a status report or a client update.
- Where it breaks
- It reads from Jira; Atlassian's page doesn't describe writing back. It works with Jira Cloud only, and filters must be starred. Atlassian says it works with up to 10,000 tickets per search. The listing shows 3.4 stars from about 215 reviews, and recent ones say the sidebar won't load or it stops working.
Jira's CSV importer
- How it works
- Save the sheet as a CSV file with File, Download. In Jira, go to Filters, Search work items, More actions and Import work items from CSV. Map each column to a Jira field, validate, and import.
- Good for
- A one-time move, like a list of tasks from a planning sheet or a backlog kept in Sheets.
- Where it breaks
- It's an upload, not a link. Each time the sheet changes, someone exports and imports again. Atlassian says people without admin rights can import 250 items per file, and the quick importer can't set parent and child tickets.
A Zapier zap
- How it works
- Zapier has Google Sheets steps like New or Updated Spreadsheet Row, and Jira steps like Create Issue, Update Issue and Find Issues (Via JQL). A zap can make a ticket for each new row, or add a row for each new ticket.
- Good for
- One steady flow, like a request form that lands in a sheet and should become a Jira ticket.
- Where it breaks
- Zapier's help center says it tracks sheet rows by row number, so sorting or deleting rows can make it skip rows or copy them twice. Each case, like a new row or a changed row, is a step you build and keep up.
Arkeo agents
- How it works
- Agents read your Jira tickets and your sheet, open tickets from new rows, keep the status in the sheet current, and nudge the owner of any ticket that has stopped moving.
- Good for
- Teams that report on Jira work in a sheet each week and spend hours keeping the two in agreement.
- Where it breaks
- Anything your rules keep for a person, like closing a ticket a client asked for, goes to the team lead in one message.
How to connect Google Sheets to Jira, step by step
These follow Atlassian's own guides. Open them for the screens.
- 1
Add Jira Cloud for SheetsIn Google Sheets, open Extensions, Add-ons, Get add-ons, and search for Jira Cloud for Sheets. Install it and allow access to your Google account.
- 2Connect your Jira site
Open the add-on from the Extensions menu, click Connect, select your Jira Cloud site and approve access.
- 3Pull tickets into the sheet
Use Get data from Jira and enter a JQL search, like one project and its open tickets, or a starred filter. Set Max Rows if you only need the top of the list, and use the add-on's Schedule tab to refresh hourly or daily. Or run a search in Jira and select Open in Google Sheets.
- 4Load sheet rows into Jira
To go the other way, download the sheet as a CSV file with a Summary column. In Jira, go to Filters, Search work items, More actions, Import work items from CSV. Map the columns, select Validate, then import.
- 5
Test one change
Move one test ticket to Done in Jira, refresh the sheet and check the status came across. Do it again after anyone renames a field or a column.
Where the Google Sheets Jira integration stops
Atlassian's add-on is a way to read Jira, not a link both ways. Its guide covers pulling tickets into a sheet. It doesn't describe sending changes back, so a status a manager fixes in the sheet stays in the sheet. Only starred filters work, and Atlassian says it handles searches of up to 10,000 tickets.
It doesn't always load. The Google Workspace Marketplace listing shows the add-on was last updated in December 2024, with 3.4 stars from about 215 reviews. Reviews from 2025 and 2026 say the sidebar shows blank, an error keeps coming back, or it stopped working for the whole team. On the Atlassian Community, people report that a sheet set to refresh each morning only updated once in a few days, and an Atlassian bug, API-563, says scheduled updates fail at random.
Going from the sheet into Jira is an upload each time. The CSV importer makes tickets once. Atlassian says people without admin rights can import 250 per file, and it warns against opening a downloaded Jira CSV in Sheets, since the file may run macros. Zapier fills the gap row by row, but its help center says sorting or deleting rows can make it miss rows or copy them twice.
And the sheet can show a ticket is late. It can't ask anyone about it. Chasing the owner, and updating the client, is still a person's job.
The agents that do it
Each agent does one job from start to finish, in your own Jira and Google Sheets. Your team talks to them in Slack or Teams.
Your developers see what customers asked for, in one place.
- Reads bug reports and requests from supportas they come
- Opens the ticket, or adds to the one that existssame day
- Links the customers who askedper ticket
Nothing sits for weeks without someone noticing.
- Checks open tickets for no updateevery day
- Nudges the owner with a commentright away
- Tells your team lead what is still lateevery day
Everyone knows where work stands without a status meeting.
- Pulls what closed, what's open and what's lateevery Monday
- Writes it in plain words for the whole teamevery Monday
- Sends it to Slack and NotionMonday morning
Questions
Is my customers' information safe?
Yes. Agents work in your own Jira and Google Sheets and see only the tickets and sheets their job needs. Customer details never go into public AI. Agents connect to AI through business-grade connections audited under SOC 2.
Is there a Google Sheets Jira integration from Atlassian?
Yes. Jira Cloud for Sheets is Atlassian's free add-on in the Google Workspace Marketplace. It pulls tickets into a sheet from a starred filter or a JQL search, and it works with Jira Cloud, not Jira Server.
Can I create Jira tickets from Google Sheets?
Yes, two ways. Download the sheet as a CSV file and load it with Jira's CSV importer, or build a Zapier zap that makes a ticket for each new row. The importer is a one-time upload; the zap runs for each new row.
Why did Jira Cloud for Sheets stop working?
Recent reviews on its listing report a blank sidebar, and Atlassian Community threads report scheduled refreshes that skip days. In one thread, Atlassian's team said to disconnect the Jira site in the add-on, connect it again and set the schedule again. If that doesn't help, a Jira site admin can open a ticket with Atlassian support.
What does it cost?
You get the price on the call, along with the hours it saves your team.
Sources
- confluence.atlassian.com: jira cloud for sheets 1528532934.html
- workspace.google.com
- support.atlassian.com: export search results
- support.atlassian.com: create issues using the csv importer
- community.atlassian.com
- community.atlassian.com
- zapier.com: jira software cloud
- help.zapier.com: Google Sheets error Zap not triggering