Yes. You can build a Jira dashboard in Google Sheets by connecting a spreadsheet to Jira with an available add-on or third-party connector, or by retrieving Jira data through its REST API. The sheet can then summarize issues, statuses, owners, and dates in tables or charts; the best method depends on your refresh needs, access rules, and comfort with setup.
What a Google Sheets Jira dashboard does
A Google Sheets Jira dashboard is a spreadsheet-based view of Jira issue data. It can be useful when a team wants to combine Jira work with other spreadsheet data, make a custom report, or share a familiar table with people who do not regularly work in Jira. Typical views include open issues by status, overdue tasks by assignee, sprint workload, and issue counts by project or priority.
It is different from a dashboard built inside Jira. Jira dashboards use Jira gadgets and permissions, and can show information close to where teams manage their work. A Sheets dashboard copies or queries selected information into a separate Google file. That flexibility comes with a responsibility: the spreadsheet may not update instantly, and its audience and permissions are managed separately from Jira.
Choose a connection method
For a straightforward report, start by checking whether an Atlassian or third-party Google Sheets connector is available and approved for your organization. A connector can guide you through Jira authentication, let you select issues with a JQL query, and provide a refresh option. Product names, pricing, supported Jira editions, and features can change, so verify the current Google Workspace Marketplace listing and your Atlassian administrator’s guidance before installing.
- Sheets add-on or connector: Usually the simplest choice for a recurring report. It may support saved queries, scheduled refreshes, and field selection, depending on the product and plan.
- Manual export: Export issues from Jira to a CSV file and open or import the file in Sheets. This is quick for a one-time snapshot but does not create an automatic connection.
- Jira REST API with Apps Script or another integration: Offers more control over data selection and refresh behavior, but requires technical setup, authentication management, and maintenance.
Jira Cloud and Jira Data Center are not interchangeable for every integration. Some connectors support only Jira Cloud, while an on-premises Jira instance may require network access, administrator configuration, or a different tool. Confirm compatibility before building the report around a connector.
Set up a basic dashboard
For an add-on, open Google Sheets in a browser, create a spreadsheet, and use Extensions > Add-ons > Get add-ons to look for a suitable Jira connector. Review its publisher, permissions, supported Jira products, and terms. Installation may be restricted by a Google Workspace administrator. After installation, follow the add-on’s own menu or sidebar to connect the Atlassian account and select a project or JQL query.
- Define the audience and purpose. Decide whether the sheet is for a project team, an executive summary, or an operational queue. This determines which fields are useful and who should see the data.
- Select a narrow issue set. Use a project filter or JQL query that returns only the needed issues. For example, a project report might include unresolved issues from one project rather than every issue the account can access.
- Choose fields deliberately. Common fields include issue key, summary, status, priority, assignee, reporter, created date, due date, and sprint. Avoid importing sensitive or irrelevant fields just because they are available.
- Load data into a source tab. Keep connector output in a tab such as “Issues” and create separate tabs for summaries and charts. This makes it easier to refresh imported rows without disrupting the dashboard layout.
- Check a few records against Jira. Confirm that the query, field values, and issue count look right before distributing the sheet.
Connector interfaces differ, so the exact query and refresh controls depend on the selected product. Do not assume that a successful first import means later refreshes will run automatically; check whether refresh is manual, scheduled, or triggered by a particular user.
Turn issue rows into useful metrics
Start with a small number of questions the dashboard should answer. A status breakdown may reveal whether work is accumulating in review, while an overdue view can help a team focus on due dates. A workload report can group issues by assignee, but issue counts alone do not measure effort: one large task may require more work than several small ones.
Suppose the imported “Issues” tab has issue keys in column A and statuses in column B, starting in row 2. With those statuses in 'Issues'!B2:B, this formula counts rows marked “In Progress”:
=COUNTIF('Issues'!B2:B,"In Progress")
If the sample rows contain the statuses “To Do,” “In Progress,” “In Progress,” “Done,” and “Blocked,” the result is 2. In Google Sheets, you can add a summary table beside the count and use Insert > Chart to create a chart from the summary range. Choose a chart that matches the question: a bar chart is often clearer than a pie chart when comparing several categories.
Define metric rules before presenting totals. For example, decide whether “open” includes only unresolved issues or every status other than Done, and whether canceled or archived work should be excluded. If the Jira workflow uses custom status names, a formula or chart that expects standard labels may omit them. Document definitions in the spreadsheet so readers do not mistake a convenient count for an official team performance measure.
Refresh timing and data quality
A spreadsheet is a snapshot of Jira data at the time it was last refreshed, unless the connector provides a live or scheduled update. Even scheduled integrations can have delays, failures, rate limits, or authorization issues. Display a “last refreshed” timestamp near the top of the dashboard if the connector supplies one; otherwise, record the update time using the connector’s documented method.
Imported data can also become incomplete if the query is too broad, the connector limits how many issues it returns, or pagination is not handled. Before relying on totals, compare the spreadsheet’s row count with Jira’s result count for the same query. Check date formats, blank assignees, custom fields, and status changes after a refresh. If rows are appended rather than replaced, watch for duplicate issues.
For a snapshot, CSV export is often sufficient. For a report people use to make current decisions, choose a connector with refresh behavior that fits the required cadence and test what happens when a refresh fails. A daily update may be adequate for a weekly planning summary but unsuitable for a live incident queue.
Security and sharing considerations
Jira permissions do not automatically control access to a copied spreadsheet. Someone who can open the Sheet may be able to see imported issue details even if they cannot access the original Jira project. Share the file only with the intended audience, review link-sharing settings, and avoid including confidential issue summaries, customer information, or internal notes unless the audience is authorized.
Consider both sides of a connector’s permissions: what Jira information it can read or change, and what access it requests in Google Workspace. Use an organization-approved integration where required. For an API-based script, keep credentials out of cells and shared documents, restrict who can edit the script, and follow your organization’s token storage and rotation rules. An administrator may need to approve the integration or API access.
Sheets versus Jira dashboards and other options
Sheets is a good fit when people need spreadsheet calculations, a custom layout, or a combination of Jira records and other data. Jira’s own dashboards are often better for a team that wants a view maintained within Jira and governed by Jira project permissions. A dedicated reporting or business-intelligence tool may be more suitable when the organization needs dashboards across many projects, durable historical trends, or managed data pipelines.
There is no single best option for every team. Compare the tools on practical criteria:
- Freshness: How often must the figures update, and what happens if a refresh fails?
- Scale: How many issues and projects are involved, and does the tool have row, query, or API limits?
- Governance: Can access to the report be limited appropriately, and are permissions reviewed by administrators?
- Maintenance: Who owns the query, connector, script, and dashboard when the original author leaves?
- Cost: Check connector subscription charges, Jira plan requirements, and any usage limits. Google Sheets access may be part of a Google account or Workspace plan, but that does not mean every Jira connector is free.
A practical approach is to prototype with a small project and a few fields, then compare the result with the equivalent Jira view. If the spreadsheet needs frequent manual repair or exposes data too broadly, move the report to a more appropriate, centrally managed tool.
Common problems and fixes
- The connection fails: Reauthorize the account if the connector reports expired access, and check whether an administrator blocks the add-on or API connection.
- Some issues are missing: Review the JQL query, the connected user’s Jira permissions, and any connector issue limits. A connector cannot return issues its account is not allowed to see.
- Counts differ from Jira: Compare the exact query and refresh time, then check pagination, duplicate rows, excluded statuses, and filters in the summary tab.
- Charts do not include new issues: Check whether the chart’s source range includes new rows. A connector that replaces or expands data may require the chart range to be adjusted.
- Custom fields look wrong: Verify the field selected by the connector and whether it returns a readable value. Some custom fields need specific configuration or may not be supported as expected.
Frequently Asked Questions
Can Google Sheets connect directly to Jira?
Sheets does not provide a universal built-in Jira connection for every account. You can use an available add-on or connector, import a CSV snapshot, or build an integration using Jira’s REST API and Google Apps Script.
Does a Google Sheets Jira dashboard update automatically?
Only if the connector or custom integration supports automatic refresh and it has been configured. Some tools require a manual refresh, and scheduled updates can be delayed or fail, so show or check the last successful update time.
Can I use JQL to choose which issues appear?
Many Jira connectors let you use JQL to define the issue set. A narrower query helps control which records are imported, but results are still limited by the connected Jira account’s permissions and by the connector’s capabilities.
Is a Sheets dashboard better than a Jira dashboard?
Not universally. Sheets offers spreadsheet analysis and flexible sharing, while Jira dashboards keep reporting in Jira and use Jira’s dashboard features and access model. Choose based on audience, data freshness, permissions, and reporting complexity.
Can I share the sheet with people who do not have Jira access?
Technically, a Google Sheet can be shared with its own audience, but imported Jira data may then be visible to people without access to the Jira project. Confirm that sharing is permitted and that the exported fields are appropriate before granting access.
Related
- Unmerge Shortcut in Excel: Windows Keys and Common Fixes
- University Budget Template in Excel: What to Include
- Unmerge Excel Cells Without Losing Data
Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.
More in Charts & pivot tables
- Excel Project Dashboard Template: Build One That WorksAn Excel project dashboard template is a workbook that turns a structured project list into a quick view…
- Excel Pivot Table Percent of Total: How to Show ItTo show a percent of total in an Excel pivot table, add the value field a second time,…
- Excel Dashboard Inspiration: Practical Ideas and Design TipsExcel dashboard inspiration starts with a clear question: what should someone understand or decide after looking at the…
- Link a Pivot Chart to a Slicer in ExcelTo link a slicer to an Excel PivotChart, select the PivotTable or PivotChart, choose PivotTable Analyze > Insert…
- Pivot Chart Slicers: How to Add and Use ThemYes. In Excel for Microsoft 365 on Windows, select the PivotChart, choose PivotChart Analyze > Insert Slicer, select…
- Power Pivot Slicers: How to Add and Connect ThemA Power Pivot slicer is a clickable filter for a PivotTable built from Excel’s Data Model. In Excel…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.