Jira Dashboard to Excel: How to Export Useful Data

Charts & pivot tables · Updated November 21, 2026

There usually isn’t a one-click way to turn an entire Jira dashboard into an Excel workbook. Instead, export the issues behind a dashboard gadget from Jira’s issue search as a CSV file, then open or import that file in Excel; charts and dashboard layout must be recreated separately if you need them in the workbook.

What exporting a Jira dashboard really means

A Jira dashboard is a page made of gadgets, not a single table of data. A gadget may show issues from a saved filter, summarize counts by status or assignee, or display a chart. Each gadget can use a different filter, project, time period, or calculation. Consequently, exporting one issue list does not necessarily reproduce everything shown on the dashboard.

For a table such as Filter Results, the useful source is usually its saved filter or JQL query. For a chart gadget, the source may be a filter whose issues can be exported, but the chart’s groupings and totals are not automatically delivered as an Excel chart. The exported CSV contains rows and columns of issue data, not the dashboard’s arrangement, colors, gadget settings, or necessarily its calculated summary.

This distinction matters when someone asks for the dashboard “in Excel.” If they need a list to sort, filter, or analyze, CSV is often enough. If they need a presentation-ready dashboard with charts and KPI summaries, treat the Jira export as source data and build the presentation in Excel.

Export the issues behind a gadget

In Jira Cloud and many Jira Data Center installations, the practical route is to open the issue search page, run the relevant saved filter or query, and export its results. Labels and navigation vary between Jira versions and interface updates, but the underlying process is much the same:

  1. Open the dashboard and identify the gadget you want to report on. Note its saved filter, project, and any settings that affect which issues it displays.
  2. Open that filter in Jira’s issue search. If the gadget uses JQL directly, copy the query into advanced issue search. For example, project = ABC AND statusCategory != Done ORDER BY updated DESC finds matching issues in project ABC that are not in a completed status category, sorted by most recently updated.
  3. Check that the search results match the gadget’s intended scope. Confirm the project, status conditions, date range, and any assignee or team restrictions before exporting.
  4. Choose the export option for CSV from the issue search results. Depending on the Jira edition and interface, the menu may offer current fields or all fields. Choose current fields for a compact report based on the visible columns, or all fields when you need additional available issue fields for analysis.
  5. Save the CSV file, then import it into Excel. Keep the original CSV if you may need to repeat the export or compare it with a later snapshot.

Jira generally limits results according to the user’s access: an export is not a way to bypass project permissions or issue security. Also, a saved filter’s sharing settings and the issues visible to the person running the export can affect what appears. If two people export the same filter and get different rows, compare their permissions as well as the query.

Choose the right fields and scope

Before exporting, decide what the spreadsheet must answer. A short list of useful columns is easier to maintain than a dump of every available field. Typical report columns include issue key, summary, status, assignee, priority, created date, updated date, due date, and project. Add fields such as sprint, component, label, or resolution only if the report actually needs them and they are available to the search/export workflow.

Use the issue key as a stable reference when people will discuss or update individual records. It is usually more dependable than a summary, which can be edited or duplicated. Include status and relevant dates if the goal is a point-in-time progress report. For trend analysis, consider exporting a consistent set of fields at regular intervals; a single export is only a snapshot and does not by itself show how the data changed over time.

Watch for differences between a gadget’s display and the issue-search results. A gadget may show only a limited number of rows, apply its own display settings, or summarize results rather than list every issue. Search results may also be subject to result limits or export limits set by the Jira environment. Verify the number of results and the query rather than assuming the dashboard’s visible count proves the export is complete.

Import the CSV into Excel

For Microsoft Excel for Microsoft 365 on Windows, importing is generally safer than double-clicking a CSV. A CSV is plain text: it does not retain Excel formulas, cell formatting, chart objects, or reliable column types. Excel may guess how to interpret values when opening it directly, which can change dates or strip leading zeros from identifiers.

  1. Open Excel and select Data > From Text/CSV.
  2. Choose the Jira CSV file. In the preview, check the file origin or encoding and confirm the delimiter is interpreted correctly. Jira exports commonly use comma-separated values, but a quoted summary can itself contain commas without being split into extra columns.
  3. Check the preview for readable characters, sensible dates, and correctly separated columns. If the preview is right, choose Load, or use the available transform option if you need to adjust data types before loading.
  4. After loading, select the data and use Insert > Table, or press Ctrl+T on Windows, if you want Excel’s table filters and structured layout. Save the result as an Excel workbook, such as .xlsx, to preserve Excel formatting and any charts you add.

Importing gives you a chance to notice problems before Excel interprets the data. For example, keep issue keys and other identifiers as text if Excel’s automatic conversion changes them. Check date columns against Jira’s displayed dates, especially if team members work across time zones or use different regional date formats. A value such as 04/05/2026 can be ambiguous between day-month and month-day conventions; verify it rather than relying on appearance alone.

On Mac, Excel’s data import options and menu labels can differ by version; use its text or CSV import workflow and inspect the preview before loading. In Excel for the web, available import and transformation controls may differ from the Windows desktop app. In either case, confirm column types and dates after opening the file rather than assuming the CSV preserved them.

Turn exported rows into a useful report

Once the data is in Excel, create a separate reporting view instead of editing the only copy of the raw export. Tables make it easier to filter and sort records, while PivotTables can summarize issue counts by fields such as status, assignee, priority, or project. For example, a PivotTable with status in Rows and issue key counted in Values can show how many exported issues are in each status.

Be clear about what a number means. A count of rows is not automatically a count of unique issues if the export or later joins have duplicated records. Likewise, a chart based on one CSV describes the exported snapshot, not live Jira activity. Add a note with the export date, filter name, and scope so a reader can tell what the report represents.

If you need to match a Jira chart, reproduce its grouping and filter conditions in Excel. A gadget that groups issues by priority may use a different set of issues than a second gadget grouped by assignee. Exporting one broad filter and applying suitable PivotTable filters can be convenient, but only if the exported fields and query cover both gadgets’ requirements.

Refreshes, recurring reports, and automation

A manually exported CSV is a point-in-time copy. It will not update when an issue changes in Jira. For occasional reporting, repeating the search and importing a fresh export may be the simplest approach. Keep the query stable and document the export date so readers do not mistake an old workbook for live status.

For recurring reporting, options include Jira filter subscriptions, a marketplace reporting or Excel integration app, and a custom connection using Jira’s APIs. These options are not interchangeable: subscriptions can deliver filter results by email, but their format and attachment behavior depend on the Jira setup and should be checked before relying on them as an Excel feed. Apps may provide scheduled exports or dashboards, but features, supported Jira editions, and prices vary by vendor.

An API-based workflow can retrieve issue data on a schedule and load it into a reporting process, but it requires appropriate authentication, access permissions, and handling for pagination, changed fields, and API limits. It also needs maintenance when a query or reporting requirement changes. For a small team’s monthly status sheet, a repeatable manual export may be safer and cheaper than building an integration; for a business-critical report, assess ownership, monitoring, and failure handling before automating it.

Dashboard export versus other reporting options

CSV export is often the best built-in starting point when the goal is to analyze issue-level data in Excel. If the primary need is to share a visual dashboard, check whether your Jira edition or installed apps offer a suitable PDF or dashboard export. A PDF is useful for a fixed visual snapshot but is not an editable Excel dataset, and it may not include every row behind a gadget.

Other choices include keeping the report in Jira, using a Jira marketplace app, or connecting a business-intelligence tool. Keeping it in Jira avoids a separate copy but may not meet spreadsheet requirements. Apps can reduce manual work, though they may have extra licensing costs and require administrator review. A BI platform may be appropriate for combining Jira with other systems, but it brings its own setup and access controls. There is no single best route: choose according to whether readers need raw rows, a formatted snapshot, ongoing refreshes, or combined analysis.

Common problems and how to avoid them

  • The spreadsheet is missing issues: Check the JQL, project permissions, issue security, search-result limits, and export option. Confirm that you opened the same filter used by the gadget.
  • Columns do not match the gadget: A gadget’s display columns and issue-search export fields may be configured separately. Adjust the search columns or choose an export option that includes the required fields.
  • Dates or identifiers look wrong: Import through Excel’s text/CSV workflow, inspect the preview, and set appropriate data types. Do not assume a CSV has stored Excel date or text formatting.
  • A chart is absent: CSV contains tabular values, not the dashboard’s chart object. Create a PivotTable or chart in Excel from the exported rows, or use a reporting tool that supports the visual output you need.
  • The workbook is stale: An exported file does not synchronize with Jira. Record when it was created and replace or refresh the source data according to a defined process.

Protect the exported data

Jira exports can contain internal project details, customer information, names, or other sensitive fields. Export only what the report requires, store the workbook in an approved location, and share it with people who are authorized to see the underlying issues. A file can be forwarded or copied outside Jira, where Jira’s permissions and audit controls may no longer protect it.

Before distributing a workbook, check hidden worksheets, extra columns, comments, and older data left in the file. If the report is recurring, define who owns the export and how outdated copies should be replaced or deleted. The convenience of Excel should not turn a narrowly shared Jira filter into a broadly circulated data extract.

Frequently Asked Questions

Can I export a Jira dashboard directly to Excel?
Usually not as a complete, editable Excel dashboard using only Jira’s standard issue export. Export the issues behind the relevant gadgets as CSV, then build the tables or charts in Excel. Availability of other export options depends on the Jira edition and installed apps.

How do I export a Jira dashboard gadget to Excel?
Open the filter or query used by the gadget in Jira issue search, check that it returns the right records, and export the results as CSV. Import the CSV into Excel, then recreate any summaries or charts you need.

Does Jira CSV export include charts?
No. A CSV is a text-based table of data, not an Excel chart or a copy of the Jira dashboard layout. Use the exported rows to create a PivotTable or chart in Excel.

Will an exported Excel file update when Jira changes?
No. A downloaded CSV or workbook is a snapshot. You must export again or set up a supported app, API, or reporting workflow to refresh data.

Why does my Jira export have fewer issues than the dashboard?
Check whether the gadget uses a different filter or scope, whether the search query includes all relevant conditions, and whether your Jira permissions or export limits affect visible results. Compare the issue keys in the search results with the gadget’s source filter.

Related

Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.

More in Charts & pivot tables

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

Spotted an error in this guide? Let us know.