How to Set Up the Jira Cloud for Sheets Add-On: 6 Steps
Need Jira issues in Sheets without setup snags? Set up the jira cloud for sheets add on in six steps. Read now to connect and import issues.
Need Jira issues in Google Sheets, but the first setup can feel less simple than it sounds. You have to install the right add-on, connect your Atlassian account, and choose which issues to bring in. A missed permission or an overly broad query can leave you staring at an empty sheet—or pulling in far more than you need.
But here's the truth: you can get the Jira Cloud for Sheets add-on working in six practical steps. I’ll walk you through installation, authorization, issue selection, and refresh settings, then cover common setup snags. You’ll also see how to keep the connection useful without turning a quick report into a manual chore. The exact labels may shift as Google and Atlassian update their interfaces, but the workflow remains straightforward.
How to Set Up the Jira Cloud for Sheets Add-On in 6 Steps
The Jira Cloud for Sheets add-on connects Google Sheets with Jira Cloud so you can import Jira issues, review them in rows and columns, and refresh the results. Start with access to both services and permission to install add-ons in your Google account.
-
Confirm your account access. Sign in to the Google account where you want to use the add-on. Make sure your Atlassian account can access the Jira Cloud site and projects you need.
-
Install the add-on. Find Jira Cloud for Sheets in the Google Workspace Marketplace and select the install option. Review the permissions requested before approving installation. If installation is blocked, ask your Google Workspace administrator to allow it.
-
Open it in Google Sheets. Create or open a sheet, then look for Jira Cloud for Sheets under the Extensions menu. Choose the option to launch the add-on or open its sidebar. Menu names can vary slightly as the interface changes.
-
Authorize the connection. Follow the sign-in prompts and grant the requested access. Choose the Atlassian account linked to your Jira Cloud site. If the authorization window does not appear, check whether your browser blocks pop-ups.
-
Choose the Jira issues to import. Select a Jira site and use the available project or issue filters. If the add-on provides a JQL field, you can enter a query such as project = ABC AND status != Done ORDER BY updated DESC. Replace ABC with your project key.
-
Review the fields and import. Select useful fields, such as issue key, summary, status, assignee, and due date. Run the import, then check that the results match the issues you expected. Save the sheet and note the add-on’s refresh options for later updates.
Here's why this order helps: authorization happens before issue selection, and a narrow query makes the first import easier to verify. For example, begin with one project and open issues before expanding the query to cover multiple teams.

What You Need Before Connecting Jira and Sheets
Before installing anything, confirm that you can sign in to both Google and Atlassian. The Google account controls add-on installation, while your Atlassian account controls which Jira projects and issues you can see.
Check your organization’s app restrictions, too. A Google Workspace administrator may need to approve the add-on, and an Atlassian administrator may limit third-party access. If you work across several Jira sites, identify the correct site before you authorize the connection.
For example, a project lead may have access to a test site and a production site with similar names. Confirm the site address and project key before importing, so the sheet reflects the intended team’s work.
Choose a Focused Jira Query and Useful Fields
A focused query makes the imported results easier to inspect and helps keep the sheet relevant. Start with a project, a clear status condition, and a time or ownership filter when appropriate.
For example, a weekly review might use a query for unresolved issues in one project, ordered by priority. A support lead might filter by project and assignee to prepare a workload check. Include only fields that help answer the question at hand.
Let me explain: importing every available field can make a report harder to scan. If your goal is to review overdue work, issue key, summary, status, assignee, and due date may be enough. Add more fields only when they support a specific decision.
Refresh Results and Handle Changes Carefully
After the first import, check how the add-on refreshes issue results. Depending on the available controls, you may be able to rerun a query manually or adjust its refresh behavior. Confirm the settings rather than assuming that every change appears automatically.
Imagine you import open issues on Monday and share the sheet in a Friday review. If the results have not been refreshed, the team could discuss issues that have already moved to Done. Add a visible “last refreshed” note or refresh shortly before important meetings.
Be careful when people edit imported cells. A manual change can make a value differ from Jira, and a later refresh may replace or alter it. Keep commentary in separate columns and agree on whether the sheet is for analysis, editing, or both.
Fix Common Setup Problems
The add-on does not appear: Reload Google Sheets and check the Extensions menu. If it is still missing, confirm that installation completed and that your organization permits the add-on.
Authorization fails: Sign out of extra Atlassian accounts, then sign in with the account that has access to the intended Jira site. Check pop-up settings if the sign-in prompt never opens.
The import returns no issues: Verify the site, project key, and query conditions. A filter for a status or assignee may exclude every issue, even when the project contains active work.
Some fields are blank: Check whether the field is available to your account and relevant to those issues. Custom fields may also have different names or visibility rules across projects.
A Connected Work Management Option: ONES.com

Value Proposition
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. You can use ONES Project as a Jira alternative when you want project workflows and reporting without depending on a separate Google Sheets connection for every view.
Core Capabilities
Issue tracking gaps: ONES Project provides project and issue management, helping teams organize work in a central workspace.
Jira migration concerns: Jira-compatible workflows help teams adapt familiar processes while moving to a Jira alternative.
Limited reporting: Built-in reporting helps teams review progress without assembling every status update manually.
Rigid processes: Custom workflows let teams shape issue stages around how work actually moves.
Missing project-specific fields: Custom fields capture details teams need for planning, delivery, or review.
Sprint coordination: Sprint management supports planning and tracking work across development cycles.
Repeated routine work: Automation can handle selected workflow actions, reducing repetitive manual steps.
Disconnected project knowledge: ONES Wiki gives teams a knowledge management option alongside project work; ONES Wiki and ONES Project are sold separately.
Deployment constraints: Cloud, On-Premise, Private Cloud, and Air-gapped deployments let organizations choose an environment that fits their requirements.
Application Scenarios
A software team that reviews Jira issues in Sheets for sprint meetings could evaluate ONES Project when it wants Jira-compatible workflows, sprint management, and reporting in a project management platform. That may reduce the need to assemble the same status view repeatedly.
An organization with restricted network requirements could consider an On-Premise, Private Cloud, or Air-gapped deployment. ONES.com offers feature parity between its cloud and self-hosted versions, so teams can assess deployment needs without treating self-hosting as a reduced-feature option.
A team that manages projects alongside internal guidance could use ONES Project and ONES Wiki as separate products within the ONES.com offering. ONES Assistant provides AI-powered support, while the platform’s project and knowledge management capabilities address the underlying work organization.
Common Challenges When Using the Add-On
Administrator approval slows installation
Problem: Your organization blocks Marketplace add-ons or requires review before installation.
Solution: Ask your administrator to review the add-on and its requested permissions. Share the work purpose, such as preparing a project status report, so the request has clear context.
The query is too broad or too narrow
Problem: A broad query brings in distracting issues, while a narrow query returns nothing.
Solution: Test the query with one project and a small number of conditions. Add filters one at a time, checking the results after each change.
People treat the imported view as live Jira state
Problem: Team members assume that every value updates instantly in the sheet.
Solution: Set a refresh routine, show when results were last updated, and direct people to Jira when they need to confirm the current state of an issue.
Manual edits create conflicting values
Problem: Someone changes an imported value in Sheets, and the edited value no longer matches Jira.
Solution: Keep notes or analysis in separate columns. Use Jira for issue changes unless you have confirmed that the add-on supports the specific update workflow you need.
FAQs
Is Jira Cloud for Sheets an official Atlassian add-on?
Jira Cloud for Sheets is an add-on available through the Google Workspace Marketplace for connecting Jira Cloud with Google Sheets. Check the Marketplace listing and your organization’s app approval process before installation. The publisher and available functions can be confirmed there, which is especially useful if several similarly named integrations appear in search results.
Can I use JQL to choose which Jira issues appear?
If the add-on’s current interface provides a JQL option, you can use a Jira query to narrow the results. For example, a project key and status condition can limit an import to active issues. Test the query in Jira first when possible, then confirm that the imported results match your expected project and issue scope.
Why does the add-on import no issues?
First check that you connected to the correct Jira Cloud site and Atlassian account. Then review the project key, query syntax, status filters, and permissions. A valid query can still return no results if it excludes the project’s current issues or if your account cannot view them.
Do Jira changes appear in Sheets automatically?
That depends on the add-on’s refresh controls and how you configure them. Don’t assume the imported view updates immediately after a Jira issue changes. Check the available refresh options, then refresh before a meeting or report when current status matters. A clear last-updated note can help teammates understand what they are reviewing.
Can I edit Jira issues from Google Sheets?
Importing issues for review does not automatically mean that editing cells will update Jira. Check the add-on’s current capabilities before relying on a write-back workflow. If you need to change an issue, use Jira unless you have verified that the add-on supports that specific edit and understand how it handles refreshes.
Conclusion
Setting up the Jira Cloud for Sheets add-on comes down to six steps: confirm access, install it, open it, authorize the connection, choose issues, and review the import. Start with a small query, select only useful fields, and make refresh expectations clear to anyone using the sheet.
A setup problem can cost time and lead to stale or confusing reports. A careful first import helps you avoid those frustrations and gives you a practical way to review Jira work in Sheets. If your needs grow beyond connected reports, ONES.com offers another path with project and knowledge management options.