How to Connect Jira Cloud to Google Sheets: 6 Easy Steps
Need fresh Jira reports without manual copying? Learn how the jira cloud for sheets add on imports issues in 6 easy steps. Read now!
Jira issues often contain the details you need for a quick status report, but copying them into Google Sheets by hand takes time. Worse, the numbers can become stale before your next meeting. If you need a repeatable way to bring Jira Cloud issues into a sheet, the Jira Cloud for Sheets add-on can help. You can install it, authorize your Atlassian account, and pull matching issues into a Google Sheet using a Jira query. Then you can refresh the results when you need an update. Here are six practical steps, plus tips for choosing fields, avoiding common setup problems, and keeping access under control. But here's the truth: a successful connection starts with a focused query, not a complicated report.
How to Connect Jira Cloud to Google Sheets in 6 Steps
Use the Jira Cloud for Sheets add-on to import Jira issues into a Google Sheet. You’ll need access to both services and permission to install Google Workspace add-ons.
-

Step 1: Check your Jira access and choose a project
Sign in to the Jira Cloud account that contains the issues you want to report on. Make sure you can browse the relevant project and view its issues.
Choose one project for your first connection. For example, a team tracking website fixes might start with the WEB project. A smaller first query makes it easier to check whether the connection works.
-
Step 2: Install Jira Cloud for Sheets
Open Google Workspace Marketplace and search for Jira Cloud for Sheets. Check that the add-on is the one you intend to use, then select the install option.
Follow the prompts to grant the requested Google permissions. Your organization may restrict add-on installations, so contact your Google Workspace administrator if you can’t install it yourself.
-
Step 3: Open the add-on in Google Sheets
Open a Google Sheet, then look under Extensions for Jira Cloud for Sheets. Choose its open or launch command to display the add-on panel.
Menu wording can change as the add-on is updated. If you don’t see it, refresh the browser tab and check that you’re signed into the Google account used during installation.
-
Step 4: Connect your Atlassian account
Use the add-on’s connection prompt to sign in to Atlassian and approve access. Review the permissions carefully and make sure you’re authorizing the account with the right Jira project access.
If your organization uses single sign-on or requires an administrator’s approval, complete that process before continuing. The connection can only return issues your Atlassian account is permitted to view.
-
Step 5: Select the issues and fields to import
In the add-on panel, choose the Jira query or issue search option. You can start with a project query, then narrow the results with filters for status, assignee, issue type, or update date.
For example, try project = "WEB" AND statusCategory != Done ORDER BY updated DESC. Select only the fields you’ll use, such as issue key, summary, status, assignee, and updated date.
-
Step 6: Import the results and refresh when needed
Run the import and check that the returned issue keys and fields look right. Compare a few rows with Jira before using the results in a report or team meeting.
When you need current results, use the add-on’s refresh or import command. If you change the query or selected fields, run the import again and review the updated columns.
Prepare a Focused Jira Query Before Importing
A focused query helps you get a useful report without bringing in every issue a project contains. Start with the project, then add only the filters that support your question.
For a weekly review, you might select open issues updated in the last seven days. For a release check, you could filter by a target version and exclude completed work. Here's why: fewer, more relevant results are easier to validate and maintain.
Choose fields that answer a specific question
If you’re tracking overdue work, issue key, summary, status, assignee, and due date may be enough. A sprint report might also need sprint name and issue type.
Each extra field can make a report harder to scan. Add a field when it supports a decision, such as identifying who owns an unresolved blocker.
Test the query with a small result set
Start with a short time range or a single issue type. If you expect ten open bugs but see hundreds of unrelated tasks, revise the filters before creating a larger report.
For example, compare the result count with the Jira issue search page. This quick check can reveal a misspelled project key or a filter that doesn’t match the team’s workflow.
Keep Imported Jira Results Useful
An import is only helpful if people understand what it shows and when it was last refreshed. Add a clear heading that names the project, filters, and reporting period.
A report called “Open WEB bugs, updated this week” is easier to interpret than one labeled “Jira export.” Include the refresh date near the top, so meeting participants can judge whether the results are current.
Refresh deliberately
Decide how often the report needs updating. A daily operational check may need a fresh import each morning, while a monthly trend review may require less frequent updates.
Before sharing a report, refresh it and confirm that the displayed results match the intended period. A scheduled meeting is a good reminder to check the refresh date.
Make changes carefully
Keep the imported issue area separate from calculations or charts where practical. If you sort, delete, or overwrite imported cells, you may make later refreshes harder to interpret.
For instance, put summary formulas in a separate section instead of editing imported status values. That keeps Jira issue details distinguishable from your own analysis.
Protect Access and Handle Connection Problems
The add-on connects services that may contain project details, customer issues, or internal work. Use an account with appropriate access and share the Google Sheet only with people who should see its contents.
When a connection fails, check the basics first: the correct Google account, the correct Atlassian account, and access to the selected Jira project. Let me explain: a working add-on cannot show an issue that the connected Atlassian account cannot view.
Review permissions and sharing
Before authorizing the add-on, review its permission prompts and follow your organization’s approval process. Avoid using a personal account for a report that belongs to a company team.
After importing, check the Google Sheet’s sharing settings. A colleague who can open the sheet may be able to see issue details even without direct Jira access.
Check query and account errors
If the import returns no issues, confirm the project key and filters in Jira issue search. A status name or field may differ from what you expect in that project.
If sign-in repeatedly fails, reconnect the Atlassian account or ask your administrator whether an organization policy blocks the add-on. A small test query can help separate an access problem from a query problem.
When a Jira-to-Sheets Connection Fits Your Workflow
Connecting Jira Cloud to Google Sheets works well when you need a flexible report, a quick calculation, or a familiar format for a meeting. It can be especially useful when a team wants to combine issue details with simple metrics.
For example, a project lead can import unresolved tasks, group them by assignee, and discuss workload during a weekly review. A product team might compare issue counts across releases before deciding where to focus testing.
But here's the trade-off: a sheet is a reporting view, not a replacement for the Jira workflow. Teams still need Jira to manage issue ownership, status changes, and project activity.
You might be wondering: is a separate report worth maintaining? It is when the report answers a recurring question and has a clear owner. If nobody refreshes or uses it, simplify the process or keep the review in Jira.
ONES.com: A Separate Option for Project and Knowledge Management
ONES.com brings project management and knowledge management together in a unified platform, while keeping those needs available as separate products. ONES Project is a Jira alternative for managing work; ONES Wiki is a Confluence alternative for organizing team knowledge.

It isn’t a Google Sheets connector, so it won’t replace the six-step import described above. It may suit teams that want project tracking and shared knowledge in one environment, including teams that need self-hosted deployment.
Core capabilities: pain, capability, result
- Work is scattered across project tools: ONES Project provides project management features, including sprint management. Teams can coordinate work in a dedicated project environment.
- Jira workflows need to be preserved: Jira-compatible workflows help teams carry familiar processes into a Jira alternative.
- Reports require extra effort: Built-in reporting gives teams project views without requiring every metric to be assembled manually.
- Different teams need different processes: Custom workflows and fields let teams reflect their own stages and information needs.
- Repeated actions take time: Automation can handle routine workflow actions, reducing manual upkeep.
- Plugins add maintenance overhead: Native capabilities can reduce reliance on plugins for supported project needs.
- Teams need control over deployment: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options.
- Self-hosted teams worry about missing features: The self-hosted versions have full feature parity with the cloud version.
- Project knowledge is separated from project work: ONES Wiki provides knowledge management separately from ONES Project, so teams can choose the products that fit.
Application scenarios
A team evaluating a Jira alternative: A team can review ONES Project’s Jira-compatible workflows, custom fields, sprints, reporting, and automation. It can compare those capabilities with its current process before deciding whether a migration is practical.
An organization with self-hosting requirements: A company that needs On-Premise, Private Cloud, or Air-gapped deployment can assess the available deployment options and feature parity. This is relevant when hosting requirements shape which project platform a team can use.
ONES.com offers a free plan for up to 30 seats. Since ONES Project and ONES Wiki are sold separately, confirm which product fits your requirements rather than assuming both are bundled.
Common Challenges and Practical Fixes
- The add-on is missing from Extensions: Confirm that installation finished under the Google account currently open. Refresh the page, then ask your administrator about organization-level restrictions if it still doesn’t appear.
- The query returns too many issues: Add a project, status, date, or issue-type filter. Run the narrower query in Jira first and check that it returns the work you expect.
- The imported results look outdated: Refresh the import and check the report’s refresh date. Set a simple reminder that matches how frequently the report is used.
- A teammate can’t see the report: Review the Google Sheet’s sharing settings and confirm the teammate has the right Google account. Also check whether their Jira access is relevant to the report’s intended use.
- Columns don’t support the report: Return to the add-on’s field selection and include only the Jira fields needed for the analysis. Re-import, then verify the column headers and a few issue rows.
Frequently Asked Questions
Is Jira Cloud for Sheets free?
Check the current Google Workspace Marketplace listing and your organization’s policies for the latest availability and terms. Installation may also depend on whether your Google Workspace administrator allows add-ons. You’ll need a Google account that can use Sheets and an Atlassian account with permission to view the Jira issues you want to import.
Can the add-on automatically keep a Google Sheet updated?
Use the refresh options available in the add-on and verify how they work for your setup. Don’t assume an import updates itself continuously. If your report supports a recurring meeting, assign someone to refresh it and check the timestamp before sharing it with the team.
Can I import only selected Jira issues and fields?
Yes. Use a Jira query to narrow the issues, then choose fields relevant to your report. For example, a workload review may need issue key, summary, status, and assignee, while a release check may need the target version. Test the query in Jira before running the import.
Why can’t the add-on show a Jira issue?
The connected Atlassian account must have permission to view the issue. Check that you authorized the right account, can open the issue in Jira, and used the correct project key and query filters. Organization sign-in rules can also affect authorization, so contact your administrator if reconnecting does not help.
Conclusion: Make the Jira-to-Sheets Connection Easy to Maintain
The Jira Cloud for Sheets add-on can bring selected Jira issues into Google Sheets through a straightforward six-step setup: install it, authorize your Atlassian account, choose a query and fields, import, and refresh.
Start with a small query, verify the results, and make refresh ownership clear. That helps prevent stale reports and gives everyone a better idea of what the sheet represents.
When manual copying gets in the way, a focused connection offers a practical fix. And if your broader need is project management rather than reporting, compare the workflow options carefully before choosing your next step.