Jira Cloud for Sheets: A Step-by-Step Setup Guide in 2026
Need Jira data in Sheets without messy exports? Set up jira cloud for sheets with clear permissions and focused queries. Read now to get started.
Jira issues are easy to track in Jira, but teams often need a familiar grid to review work, share status, or prepare reports. Setting up a connection to Google Sheets can save manual copying, yet the wrong permissions or query can expose more issues than you intended. Add-on availability and interface labels may also change, making older setup instructions frustrating to follow.
But here's the truth: a reliable setup starts with a small test, clear access permissions, and a query that returns only the issues you need. Follow these steps to connect Jira Cloud and Google Sheets in 2026, check that the results are accurate, and establish a refresh routine. You’ll also learn what to verify before sharing the sheet with your team.
How to connect Jira Cloud to Google Sheets
Use the steps below to install the available connector, authorize the right account, and bring a controlled set of Jira issues into Google Sheets. Your exact menus may vary by add-on version and organization settings.
-
Check add-on availability and permissions. Ask your Google Workspace or Atlassian administrator whether third-party add-ons are allowed. Confirm that the Jira account you plan to connect can view the project and issues you need.
In 2026, availability can depend on your organization’s policies and the current Marketplace listing. Verify that the add-on is available and approved before you build a workflow around it.
-
Create a test sheet. Start with a new, restricted Google Sheet rather than a team-wide report. This lets you test the connection without exposing issue details to people who should not see them.
Choose a small project or a limited set of sample issues. A compact test makes it easier to spot missing fields, unexpected results, and permission problems.
-
Install the Jira connector. In Google Sheets, open the add-on or extension menu and use the option for finding add-ons. Search for the Jira Cloud for Sheets connector, then review its publisher, permissions, and current availability.
If your organization distributes approved add-ons through an administrator, follow that process instead. Avoid installing a similarly named add-on before confirming it is the one your organization permits.
-
Authorize your Jira account. Open the installed connector and follow its sign-in or authorization prompts. Choose the Jira Cloud site you intend to use, then review the access request before approving it.
Use an account with the minimum Jira permissions needed for the task. If authorization fails, check whether your administrator restricts third-party access or requires an approval step.
-
Select issues with a query or project filter. Use the connector’s available search options, such as a project selection or JQL query, to limit the issues you bring into the sheet.
For example, a project team might start with open issues assigned to a particular sprint. Check the query in Jira first, then use the same criteria in the connector when supported.
-
Choose fields and import the results. Select only the fields needed for your task, such as issue key, summary, status, assignee, and due date. Run the import and compare several rows with their Jira issues.
Confirm that dates, statuses, and user names look correct. If the connector offers refresh or update options, test them with a small set before relying on them for routine work.
-
Set a refresh routine and share carefully. Refresh the results when your team needs current information, following the connector’s available controls. Keep the sheet’s sharing permissions aligned with the Jira project’s access rules.
Before sending a link, check who can view or edit the sheet. Jira access and Google Sheets access are separate, so a person may be able to see a copied issue detail even without access to the Jira project.

What to prepare before connecting the two services
Start by defining the purpose of the connection. A sprint review may need issue keys, owners, status, and estimates, while an operations report may need priority, component, and resolution date.
Here's why: every extra field makes the sheet harder to review and may expose information people do not need. If you are preparing a weekly status view, begin with a narrow selection and add fields only when someone can explain why they matter.
Check both sides of the connection. Your Google account must be allowed to install or use the add-on, and your Jira account must be able to view the projects and issues you want to retrieve.
Keep one person responsible for the first setup. That person can record the selected query, fields, and refresh approach, so teammates understand what the report includes and how current it is.
Choose a Jira query that fits the report
A good query keeps the results relevant. For example, a product team could use a project filter and an active sprint condition to review only work in progress, rather than importing every issue in the project.
Let me explain: a broad query can make the sheet slow to scan and can include closed or unrelated work. Test the criteria in Jira’s issue search before using them in the connector.
Think about who will use the results. A team lead may need assignee and priority, while an executive summary could work with issue key, status, and a small set of counts.
When the report has a recurring purpose, name the sheet and its tabs clearly. Labels such as “Open sprint issues” help readers understand the view without asking how it was created.
Verify imported issues and refresh behavior
After the first import, compare several rows with the corresponding Jira issues. Check that the issue key links to the expected item and that fields such as status and due date match.
The best part? A five-minute review can catch a misleading report before it reaches a larger audience. Test an issue that changed recently, then confirm whether a refresh updates its values as expected.
Find out whether refresh is manual, scheduled, or controlled by another setting in your connector version. Don’t assume the sheet updates instantly whenever someone changes an issue in Jira.
Add a visible “last checked” note if readers might mistake an older snapshot for live status. A timestamp gives a quick signal about when the results were last reviewed.
Protect access and keep the workflow understandable
Jira permissions do not automatically control who can open a Google Sheet. Anyone with access to the sheet may see the issue details it contains, even if they cannot open those issues in Jira.
You might be wondering: what should you do before sharing? Review the sheet’s viewer and editor list, remove unnecessary access, and avoid publishing a link with broad permissions.
Limit sensitive fields, especially when the report is intended for a wider audience. Issue summaries, comments, and customer details can reveal more than a simple status report requires.
Document the query, the fields selected, and the person responsible for refreshes in a short note inside the sheet. This gives teammates enough context to check the report without relying on informal handoffs.
ONES.com Solution: ONES.com
ONES.com brings project management and knowledge management together on one platform, with AI support through ONES Assistant. ONES Project handles project and task management as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

If a Google Sheets connection is becoming a second place to maintain project status, you may want to assess whether your team’s workflow can live directly in a project management platform. ONES Project supports Jira-compatible workflows, sprint management, custom fields, automation, and built-in reporting. It can help teams track work and review progress without relying on repeated manual exports.
Core capabilities
- Issue status is scattered across reports: ONES Project provides built-in reporting, helping teams review project progress in the platform where the work is managed.
- Jira workflows need to be preserved: Jira-compatible workflows help teams carry familiar processes into a Jira alternative.
- Teams need different approval paths: Custom workflows let teams shape transitions around how work moves through their organization.
- Standard fields miss key details: Custom fields let teams record project information that matters to their process.
- Sprint work needs closer coordination: Sprint management supports planning and tracking work within an iteration.
- Repeated actions take time: Automation can handle eligible routine steps, reducing manual follow-up.
- Extensions add maintenance overhead: Native capabilities can reduce reliance on plugins for common project workflows.
- Hosting requirements restrict cloud adoption: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.
Application scenarios
A software team preparing sprint reviews: A team that regularly pulls issue details into Sheets for status meetings could assess ONES Project’s sprint management and built-in reporting. This may make routine review work easier to manage alongside the project itself.
An organization with restricted networks: A team that cannot use a public cloud service for project work can consider ONES.com’s On-Premise, Private Cloud, or Air-gapped deployment options. The organization can evaluate the deployment against its own security and operational requirements.
A team maintaining project knowledge: A team that needs both project tracking and a separate knowledge base can assess ONES Project and ONES Wiki as distinct products within the ONES.com platform. Each can serve its respective project management or knowledge management needs.
Common challenges and practical fixes
The add-on is unavailable or blocked
Problem: Your organization’s administrator may block add-on installation, or the connector may not appear in your available Marketplace options.
Solution: Ask your administrator to check the current listing and approval policy. Don’t work around an organization’s security controls by installing an unapproved connector.
Authorization succeeds, but issues are missing
Problem: The connected Jira account may not have permission to view every project or issue in the query.
Solution: Check the account’s project access and test the query while signed in to Jira. If an issue remains unavailable, ask a Jira administrator to review its permissions.
The imported results appear outdated
Problem: A sheet can show an earlier snapshot if no refresh has run since an issue changed.
Solution: Confirm how refresh works in your connector version and set a routine that matches the report’s purpose. Add a last-checked time so readers can judge its freshness.
People see details they should not access
Problem: A broad Google Sheets sharing setting can reveal copied Jira details to people outside the project.
Solution: Restrict viewers and editors, remove unnecessary fields, and review sharing before distributing the link. Treat the sheet’s access list separately from Jira project permissions.
FAQs
Can I connect Jira Cloud to Google Sheets in 2026?
It may be possible through a Jira Cloud for Sheets connector, but availability depends on the current add-on listing and your organization’s installation policies. Check the Marketplace option available to your Google account and confirm approval with your administrator. If the add-on is unavailable, ask your administrator about an approved integration method rather than installing an unverified alternative.
Do I need Jira administrator access to import issues?
You generally need permission to install or authorize the connector through your organization’s policies, plus Jira access to the projects and issues you want to retrieve. You do not necessarily need Jira administrator privileges to view issues. If the connection is blocked or returns incomplete results, ask an administrator to check the access policy and the connected account’s project permissions.
Will the Google Sheet update automatically when a Jira issue changes?
Do not assume it will. Refresh behavior depends on the connector’s current features and settings, which may include manual refresh or other update controls. Test a recently changed issue and confirm how the results behave. If the report is used for decisions, show when it was last checked so readers can distinguish a current view from an older snapshot.
Can I edit Jira issues from Google Sheets?
That depends on the connector’s current capabilities and the permissions granted to your connected Jira account. Treat an import as read-only until you have verified whether updates are supported, which fields can be changed, and how those changes reach Jira. Test any edit function with a low-risk issue and confirm the result in Jira before using it for regular team work.
How can I keep Jira issue details private in Sheets?
Use a restricted sheet, import only the fields required for the task, and review the viewer and editor list before sharing. Jira project permissions do not automatically restrict access to details copied into Google Sheets. If the sheet includes sensitive summaries or customer information, keep access limited and remove those fields from reports that do not need them.
Conclusion
Connecting Jira Cloud to Google Sheets can make reviews and reporting more convenient when you control the query, confirm the results, and manage access deliberately. Start with an approved connector and a small test, then check refresh behavior before relying on the report.
Manual exports can become frustrating when teams need frequent updates or maintain several views. A focused setup helps you avoid unnecessary copying while keeping issue details visible only to the right people. If the reporting workflow grows into a second project tracking system, evaluate whether ONES Project or another suitable workflow can manage the work more directly.