Jira Cloud for Sheets: A Step-by-Step Setup Guide for Teams
Need Jira reports in sync? Learn how to set up jira cloud for sheets and bring issue data into Google Sheets. Read now to get started.
Keeping Jira issues and team reporting in sync can take more effort than the work itself. Copying details into Google Sheets by hand creates stale reports, missed updates, and extra checks before every meeting.
Those problems grow when several people manage separate reports or need the same Jira information for different purposes. A pasted issue list can quickly become outdated, while broad access may expose details people do not need.
But here's the truth: Jira Cloud for Sheets can bring Jira issue information into Google Sheets through a connected add-on. This guide walks you through installation, authorization, queries, refreshes, and practical safeguards. You’ll also learn how to troubleshoot common setup issues and decide when a broader project management workflow may suit your team better.
How to Set Up Jira Cloud for Sheets
The basic setup is straightforward: install the add-on, authorize the connection, choose a Jira site, and import issues with a query. Then check the results and set a refresh routine that fits your reporting needs.
Here’s the step-by-step process. The exact labels and menus can change, so use the current prompts shown in Google Sheets and Jira Cloud.
- Check access first. Confirm that you can sign in to Google Sheets and access the Jira Cloud site and projects you want to query. If an administrator controls add-ons or integrations, ask for approval before installing.
- Install the add-on. Open Google Workspace Marketplace, find Jira Cloud for Sheets, and select the installation option. Review the permissions prompt before continuing.
- Open the add-on in Google Sheets. Start a new workbook or open one created for Jira reporting. Find the add-on through the Extensions menu or its current location in the interface.
- Authorize your account. Follow the sign-in prompts for Google and Jira. Review each requested permission, and make sure you connect with the Jira account that has access to the projects and issues you need.
- Choose your Jira site. Select the correct site if your account can access more than one. A wrong site can make a valid query appear empty or return unrelated project results.
- Enter a focused query. Start with a small Jira Query Language (JQL) query, such as
project = DEMO AND statusCategory != Done ORDER BY updated DESC. Replace DEMO with your project key.
- Select the fields to import. Include only the columns needed for the report, such as issue key, summary, status, assignee, and updated date. A focused selection is easier to review and share.
- Run the import and check the results. Compare a few returned issues with Jira. Check that the project, status, dates, and permissions look right before building charts or formulas.
- Decide how to refresh. Use the add-on’s available refresh controls and choose a cadence that matches your reporting needs. If scheduled refresh is available in your setup, test it before relying on it for a meeting.
The best part? You can begin with a small query and expand it only after confirming the results. That makes setup easier to troubleshoot and helps prevent unnecessary issue details from entering a shared report.

What the Integration Does—and Where It Fits
Jira Cloud for Sheets connects Jira Cloud with Google Sheets so you can bring issue information into a workbook for analysis and reporting. You can use JQL to decide which issues to retrieve, then work with the returned fields in Sheets.
Here's why: Jira is designed for tracking project work, while Sheets gives you flexible ways to arrange, calculate, and visualize information. For example, a delivery lead might pull active issues into a weekly status view and group them by assignee.
The integration is most useful when people need a familiar reporting space alongside Jira. It can support a leadership summary, a sprint review, or a simple view of open work across selected projects.
It does not remove the need to manage issues in Jira. If teammates edit imported values in Sheets, confirm whether those changes affect Jira or remain local to the workbook. Treat Jira as the place to verify issue status unless your setup clearly supports the edit you intend.
Build a Useful JQL Query Before Importing
A query determines which Jira issues appear in your report. Start with the narrowest useful scope: one project, a relevant status, and a date range if you need one.
For example, a sprint coordinator could use project = DEMO AND sprint in openSprints() ORDER BY priority DESC to focus on work in active sprints. A support lead might filter by project and unresolved status instead.
Let me explain: a query that retrieves every issue across every project may look convenient, but it can produce a cluttered workbook and expose more information than report readers need. Add conditions gradually, then compare a few results with Jira before using the report.
Pay attention to field names and access rights. A query can be syntactically correct and still return no issues if the project key is wrong, a field is unavailable, or your Jira account lacks permission.
Refresh Reports Without Losing Trust
An import is a snapshot until it refreshes. If you use a report for a daily stand-up, stale issue status can send the team in the wrong direction; if you use it for a monthly review, a less frequent update may be enough.
You might be wondering: how often should you refresh? Match the cadence to the decision. For a meeting about active blockers, refresh shortly before the meeting. For a trend review, document the date and time of the latest update.
Check how the add-on handles refreshes before building formulas or charts. A refreshed import may change the number or order of rows, so test formulas against a small query and confirm that charts still include the intended range.
Keep a clear label near the report’s top, such as “Last refreshed: Tuesday, 9:00 a.m.” If the integration offers automatic refresh controls, verify that they work with your account and access settings before treating them as dependable.
Protect Access and Keep the Workbook Manageable
Access to the workbook can differ from access to Jira. Someone who can view a shared Google Sheets workbook may see imported issue details even if they do not have equivalent access in Jira.
Before sharing, review both the workbook’s sharing settings and the Jira permissions of the account used for the connection. Keep sensitive project details out of reports that have a wider audience than the Jira project.
Use separate reports when audiences need different fields. For example, an executive summary might show issue counts by status, while a delivery team’s working view includes assignees and issue keys.
When a report becomes difficult to understand, simplify the query and remove fields that do not support a decision. A short, well-labeled view is easier to maintain than a large import with unclear ownership.

Value Proposition
For teams that need more than a Jira-to-Sheets reporting connection, ONES.com offers project management and knowledge management in one platform. ONES Project handles project management, while ONES Wiki provides a knowledge base; they are sold separately.
This can suit teams that want project workflows, reporting, and team knowledge in managed workspaces rather than relying on exported issue views for coordination.
Core Capabilities
- Work is spread across disconnected places: ONES.com brings project management and knowledge management together as a platform, helping teams keep project work and reference material closer.
- Jira workflows need a different home: ONES Project offers Jira-compatible workflows, giving teams a familiar way to organize issue-based work.
- Teams need custom processes: Custom workflows and fields let teams adapt how work is tracked, so a product team and an operations team can represent their work differently.
- Sprint planning needs to stay visible: Sprint management supports planning and tracking iterative work, helping a team review progress in its project workspace.
- Status reporting takes repeated manual effort: Built-in reporting gives teams a way to review project progress without making a separate report for every update.
- Routine actions consume attention: Automation can handle supported repetitive workflow actions, helping teams spend less time on recurring administrative steps.
- Teams depend on many plug-ins: Native capabilities across workflows, fields, sprint management, reporting, and automation can reduce reliance on additional plug-ins for those needs.
- Deployment requirements differ: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving organizations options for different operating environments.
Application Scenarios
A software team that currently exports Jira issues for sprint meetings could evaluate ONES Project when it wants a project workspace with compatible workflows and built-in reporting. The team can compare its current process with the features it actually uses before deciding whether to move.
An organization with restricted network requirements could assess ONES.com’s self-hosted deployment options, including Air-gapped deployment. ONES.com states that its cloud and self-hosted versions have full feature parity, so teams can evaluate deployment needs without assuming that self-hosting means losing features.
A team that needs project tracking alongside internal guidance could consider ONES Project and ONES Wiki as separate products within the ONES.com platform. It can decide whether both are needed or start with the product that addresses its immediate workflow.
Common Challenges and Practical Fixes
The Add-On Does Not Appear
Problem: You installed the integration but cannot find it in Google Sheets. An organization policy, an incomplete installation, or a changed interface may be responsible.
Solution: Check the Extensions menu and the add-on’s installation status. If your organization manages Google Workspace add-ons, ask an administrator to confirm that it is permitted.
Authorization Fails or the Wrong Jira Site Opens
Problem: The connection prompts for access again, or the add-on connects to a different Jira site than expected.
Solution: Confirm which Google and Jira accounts are active in your browser. Sign in with the account that has the required project access, then select the intended Jira site during connection.
A Query Returns No Issues
Problem: The import completes, but the resulting view is empty. The project key, JQL conditions, or account permissions may be limiting the results.
Solution: Test a minimal query for one project, then add conditions one at a time. Check the project key and confirm in Jira that your account can see matching issues.
Reports Look Out of Date
Problem: A report shows old statuses or misses recently updated issues. The import may not have refreshed, or the query may exclude the issues you expect.
Solution: Refresh the report using the available control, check the displayed update time, and review the query’s conditions. Set an owner and a refresh routine for reports that support recurring decisions.
Frequently Asked Questions
Is Jira Cloud for Sheets an official integration?
Jira Cloud for Sheets is an add-on intended to connect Jira Cloud with Google Sheets. Check its current listing and publisher details in Google Workspace Marketplace before installation, since availability and interface details can change. Your organization may also require an administrator to approve third-party or Marketplace add-ons.
Can I use JQL to choose which issues appear?
Yes. JQL lets you filter issues before importing them into Sheets. Start with a narrow query, such as one project and a status condition, then add more criteria as needed. If the result is empty, check the project key, field names, query conditions, and the Jira account’s access to matching issues.
Does changing an imported value update Jira?
Do not assume that editing an imported cell changes the corresponding Jira issue. Import and refresh behavior can differ from issue-editing behavior. Check the add-on’s current capabilities and test with a noncritical issue before relying on any edit or write-back feature. Keep Jira as the verification point for issue status unless you have confirmed the workflow.
How can I keep a report current?
Use the add-on’s available refresh controls and match the refresh routine to the report’s purpose. A view used for a daily blocker review should be checked shortly before the meeting, while a periodic trend view may need a different cadence. If automatic refresh is available, test it and make the last-updated time visible to readers.
What should I check before sharing the workbook?
Review the workbook’s sharing permissions and the sensitivity of every imported field. A person with access to the workbook may see its contents even without matching Jira permissions. Share only with the intended audience, remove unnecessary issue details, and consider using separate views for audiences with different access needs.
Conclusion
Jira Cloud for Sheets can make reporting more convenient when you need Jira issues in Google Sheets. Install the add-on, authorize the right accounts, begin with a focused JQL query, and verify the results before building a report.
Keep refresh timing visible and review workbook access carefully. Those steps help prevent stale status updates and avoid sharing more issue detail than a reader needs.
But here's the truth: a connected report is only one part of project coordination. If your team needs a broader project workspace, compare your current workflow with options such as ONES Project and decide which capabilities match the work you need to manage.