Google Sheets Jira Add-On: Setup, Features, and Limits

How-to basics · Updated November 20, 2026

Yes—Atlassian’s Jira Cloud for Sheets add-on connects Jira Cloud with Google Sheets so you can bring Jira issues into a spreadsheet, use a JQL query to select them, and refresh the imported data. Install it from Google Workspace Marketplace, authorize access, and open it from the Extensions menu in a Sheet; it is a reporting and analysis option, not a replacement for Jira.

What the Jira add-on for Google Sheets does

Google Sheets does not include a built-in Jira connector in its standard menus. The add-on provides a link between a Sheet and a Jira Cloud site, allowing a user to retrieve issue information without manually copying every row. You can choose which issues to bring in with Jira Query Language (JQL), then work with the resulting rows using familiar spreadsheet features such as sorting, filters, charts, and formulas.

This can be useful when a team wants a lightweight report, a cross-project overview, or a spreadsheet-friendly view of work. For example, a project coordinator could retrieve open issues for one project, include fields such as issue key, summary, assignee, priority, and status, and create a chart showing how many issues are in each status. The spreadsheet is a snapshot of Jira data at the time of import or refresh; it should not be treated as a live dashboard that updates every second.

The add-on is intended for Jira Cloud. It is distinct from Jira’s own CSV export and from third-party data connectors, which may offer different scheduling, transformation, or write-back features.

How to install and connect it

Start in Google Sheets in a web browser. The names and placement of add-on controls can change as Google and Atlassian update their products, but the usual setup is:

  1. Open a spreadsheet and choose Extensions > Add-ons > Get add-ons.
  2. Search Google Workspace Marketplace for Jira Cloud for Sheets and check that the publisher is Atlassian before installing.
  3. Accept the requested Google permissions. Then return to the spreadsheet and open Extensions > Jira Cloud for Sheets, followed by the available open or launch command.
  4. Sign in to the Atlassian account that has access to the relevant Jira Cloud site, and approve the connection if prompted.
  5. Select a site, provide a JQL query or use the add-on’s available issue-selection controls, choose the fields to retrieve, and run the import.

Google and Atlassian authorization are separate parts of the connection: installing the add-on does not give an account access to Jira projects it could not already view. If a site or project is missing, first check that you are signed in to the correct Atlassian account and have permission to browse the relevant issues. An organization administrator may also control which Marketplace apps users can install or authorize.

Using JQL to choose issues

JQL is Jira’s query language. It lets you define the issue set before it reaches the spreadsheet, which is usually better than importing a large project and trying to filter it afterward. A simple query might be project = ABC AND statusCategory != Done ORDER BY updated DESC. This asks for issues in project ABC that are not in the Done status category, with recently updated issues first.

JQL fields and values depend on the Jira site. A project key such as ABC must exist in your Jira instance, and custom fields can have site-specific names. You can add conditions for assignee, issue type, labels, or dates, but check Jira’s own query interface if a field name or value is rejected. The add-on does not make a query more permissive than your Jira account: it can only return issues that account is allowed to see.

Before importing, decide what the spreadsheet is for. A status report may need only the issue key, summary, owner, status, priority, and update date. A broad export of every field can make a Sheet harder to read and may expose details that are irrelevant to the audience. If a query returns too many issues, narrow it by project, status, date, or another useful condition rather than assuming the spreadsheet can handle an unlimited dataset.

Refreshing and working with imported data

After the first import, use the add-on’s refresh or import controls when you need an updated view. A refresh retrieves current Jira values for the configured selection; it does not mean that every change in Jira appears instantly in the spreadsheet. The refresh interval and available controls depend on the add-on’s current interface and capabilities, so check its menu or help information rather than relying on an assumed automatic schedule.

Once the data is in Sheets, you can use standard Google Sheets tools. For instance, select the header row and choose Data > Create a filter to filter the displayed records, or use Insert > Chart to visualize counts. Keep analysis separate from the imported table when practical: a second tab for summaries makes it easier to refresh the source data without disturbing formulas, notes, or chart inputs.

Be careful when sorting or editing imported rows. A row number is not a stable identifier, and a refreshed result may be ordered differently if the query changes. Use Jira’s issue key to identify a record. If collaborators add manual notes, place them in a separate table keyed by issue key instead of relying on a note staying beside a particular imported row after a refresh.

What it does not automatically do

A common misconception is that connecting a spreadsheet means edits will synchronize in both directions. Importing Jira issues into Sheets does not, by itself, make every cell an editable Jira field or guarantee that a change in a cell updates the corresponding issue. Treat the imported range as report data unless the current add-on explicitly provides a supported action for creating or updating Jira issues.

Likewise, refreshing is different from continuous synchronization. A refreshed row can show a newer Jira status, but changes made only in the spreadsheet may be overwritten or left out of Jira. If you need a controlled bulk-edit workflow, verify the add-on’s documented write-back features and restrictions first, or make changes in Jira using an approved Jira workflow. Do not assume that formulas, comments, formatting, or added columns will be understood by Jira.

The add-on also does not replace Jira permissions, issue history, workflow rules, or project configuration. A spreadsheet can present selected fields conveniently, but Jira remains the system of record for issue ownership and status unless your organization has deliberately configured another process.

Common uses and practical limits

Typical uses include a weekly project status report, a list of overdue work, an issue inventory for a planning meeting, and a simple comparison of work across projects. A support lead might query unresolved high-priority issues updated in the last week, then share a read-only Sheet with stakeholders who need an overview but do not need to work directly in Jira.

Spreadsheets are less suitable for very large or frequently changing Jira datasets, complex relational analysis, or operational workflows where every update must be tracked and validated. Import limits, response time, and available fields can depend on Jira, Google Sheets, and the add-on’s current implementation. For a large extract, try a narrowly scoped query first and confirm that the fields and issue count are appropriate before building a report around them.

Also consider how the Sheet will be shared. Jira access controls do not necessarily protect a copy of issue data once it has been imported into a Google Sheet. Anyone granted access to the spreadsheet may be able to see its contents according to the Sheet’s sharing settings, even if that person would not normally have access to the Jira project.

Cost, permissions, and data safety

Check the Google Workspace Marketplace listing for the add-on’s current price and terms. The connector may be available without a separate purchase, but that does not make Jira itself free: Jira access is subject to the organization’s Atlassian subscription and account permissions. Paid third-party connectors may have separate pricing, usage limits, and data-processing terms.

Review requested permissions before authorizing an app, especially when connecting a work account. Use the minimum Jira access needed for the report, limit the Sheet to the intended audience, and avoid importing sensitive fields unless they are necessary. If the report is no longer needed, remove access to the Sheet and follow your organization’s process for disconnecting apps or revoking account access. Administrators should assess Marketplace app policies and data-handling requirements before deploying a connector broadly.

Alternatives to the add-on

For a one-time, small export, Jira’s built-in issue search and export options may be enough; the exact export formats available depend on the Jira interface and account. A CSV can be opened or imported into Sheets, but it is a static file: getting new Jira values generally means exporting again. That can be simpler when a connection is unnecessary.

For scheduled reports, larger datasets, or transformations across several systems, compare reputable third-party Jira-to-Sheets connectors and reporting tools. Check whether they support your Jira deployment, refresh schedules, custom fields, issue limits, and write-back needs. An API-based integration can provide more control, but it requires someone to manage authentication, permissions, errors, and maintenance. For routine project tracking, Jira’s own dashboards and filters may be more appropriate than copying data into another service.

Troubleshooting connection and import problems

If the add-on does not appear, confirm it finished installing and reload the spreadsheet. If the Jira command is present but sign-in fails, check which Google and Atlassian accounts are open in the browser; using a personal Atlassian account instead of a work account is a frequent source of confusion. Your Workspace or Atlassian administrator may also restrict third-party apps.

If an import returns no issues, test the JQL in Jira’s issue search while signed in to the same Atlassian account. Check the project key, status value, date conditions, and access permissions. If only some expected fields are missing, confirm that the fields are available to that account and selected in the import configuration. For an error that persists after these checks, consult the add-on’s current Marketplace support information or your Jira administrator, since error messages and menus can change with product updates.

Frequently Asked Questions

Is the Jira add-on for Google Sheets free?

Check the current Google Workspace Marketplace listing for the add-on’s price and terms. Even if the add-on has no separate charge, using Jira Cloud still requires the appropriate Atlassian account, subscription, and project access.

Can Google Sheets update Jira issues through the add-on?

Do not assume that editing an imported cell updates Jira. The basic import-and-refresh workflow is for bringing issue data into a Sheet; verify the add-on’s current documentation for any supported create or update actions before planning a write-back process.

Does Jira Cloud for Sheets work with Jira Data Center?

The add-on is designed for Jira Cloud. Organizations using Jira Data Center or another self-managed deployment should check the Marketplace listing and their administrator’s guidance, or consider an integration that explicitly supports their deployment.

How do I refresh Jira data in Google Sheets?

Open the Jira Cloud for Sheets controls from the Extensions menu and use the available refresh or import action for the configured query. The result is updated when that action runs; it is not necessarily a live, continuously synchronized view.

Can I use JQL with the add-on?

Yes. JQL can specify which issues to import, such as open issues in a project or issues updated after a chosen date. Query results remain subject to the Jira account’s permissions and the add-on’s supported import limits.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.