You generally cannot export an entire Jira dashboard, with all its gadgets and charts, directly to an Excel workbook using a single built-in command. To work in Excel, export the issues behind a dashboard gadget or filter as a CSV file, then open or import that file and save it as an .xlsx workbook.
The key is to decide whether you need the underlying issue records or a copy of the dashboard’s visual layout. Those are different things: a spreadsheet can hold rows and columns of Jira data, but it does not automatically recreate a dashboard’s charts, gadget arrangement, or interactive filters.
What Jira can and cannot export
A Jira dashboard is a page assembled from gadgets. A gadget may show a list of issues, a chart, a count, or a summary based on a saved filter or project. The dashboard itself is not normally one spreadsheet table, so Jira cannot reliably turn every gadget on the page into a single Excel sheet while preserving its meaning and appearance.
Jira’s issue search is usually the practical starting point. You can run a search or saved filter that matches the issues shown by a gadget, then use the issue-search export controls. In Jira Cloud, the available export choices commonly include CSV options such as current fields or all fields. Labels and choices can change with Jira’s interface and configuration. Jira Data Center versions and installed apps may offer different options, so check the export menu in your own instance rather than assuming every deployment has an Excel button.
A CSV is a plain-text data file, not an Excel workbook. Excel can open it, but charts, formatting, formulas, and multiple worksheets are not carried over from Jira. To produce a native workbook, open or import the CSV in Excel and save a copy as an Excel Workbook (.xlsx).
Export the issues behind a dashboard gadget
For a useful export, identify the gadget’s data source before downloading anything. Many gadgets use a saved Jira filter; other gadgets may use a project, a selected date range, or a configuration that calculates a summary. If you export a broader search than the gadget uses, your spreadsheet will not match the dashboard.
- Open the dashboard and inspect the gadget you want to reproduce. Note its filter, project, date range, and any other visible criteria. If the gadget links to a saved filter, open that filter.
- Go to Jira issue search and run the same filter or search criteria. If necessary, use the advanced search interface and review the JQL, Jira’s query language, rather than guessing from the chart alone.
- Choose the fields you need in the search results. Common choices include issue key, summary, status, assignee, priority, project, and created or due date. The available columns depend on the fields and permissions in your Jira site.
- Use the issue search page’s export menu and select an available CSV option. Choose a current-fields export when you want the visible columns, or an all-fields option when you need additional issue fields and are prepared to clean up the result.
- Open the downloaded CSV in Excel, check that the columns and values were interpreted correctly, and save a separate .xlsx copy if you need workbook features.
For example, if a dashboard’s Filter Results gadget displays unresolved defects assigned to one team, export that same saved filter rather than exporting every issue in the project. The spreadsheet will then contain issue-level records that can be sorted, filtered, or summarized. A pie chart gadget, by contrast, may show only totals by status; the export of its source filter contains the individual issues, not necessarily a replica of the chart.
Choose the right fields and export scope
Decide what question the spreadsheet needs to answer before selecting fields. A compact export is easier to check and share. An all-fields export can be helpful for analysis, but it may contain many columns that are irrelevant to the task, and some fields may have complex or lengthy values.
- For a status report: include issue key, summary, status, assignee, priority, and the relevant date fields.
- For workload review: include assignee, team or project fields if available, status, and estimates. Confirm how your Jira site represents estimates before comparing them.
- For a chart: export the category field and the issue-level records that contribute to the count. A gadget’s total may be based on a filter, permissions, or date range that must also be reflected in the export.
- For audit or follow-up: include stable identifiers such as issue key and capture the export date and filter name in the workbook, so readers can understand what was included.
Do not assume that a dashboard’s visible total means every viewer sees the same underlying issues. Jira permissions can limit which issues a user can view. The export reflects the access and search results available to the person exporting, not necessarily every issue in the organization.
Open the CSV safely in Excel
On Windows with Microsoft 365, you can open the downloaded CSV in Excel and then use File > Save As to create an .xlsx workbook. For more control over interpretation, use Data > From Text/CSV, inspect the preview, and load the data. This import route is useful when values such as dates, identifiers, or text fields need careful handling. On Mac, opening the CSV in Excel is also an option; import controls and labels can differ by Excel release, so check the Data tab if you need to specify how the file is interpreted.
Keep the original CSV unchanged until you have checked the workbook. A CSV does not preserve Excel formatting or formulas, and opening it directly may lead Excel to interpret some values automatically. For example, date formats can display differently according to regional settings, and long numeric-looking identifiers may be treated as numbers. Jira issue keys contain letters and digits, but other exported fields might include values where preserving the original text matters.
After import, verify a few records against Jira. Check that commas or line breaks inside descriptions did not shift information into unexpected columns, that dates look plausible, and that the row count is consistent with the search results. If the export is intended for recurring analysis, save a clean workbook template separately instead of repeatedly overwriting the source file.
Why the spreadsheet may not match the dashboard
A mismatch does not necessarily mean the export failed. Dashboard gadgets can apply their own settings, and not all gadgets display raw issue records. A chart might group issues by status, while a Filter Results gadget lists only a chosen number of columns or rows. A time-based gadget may use a time window or calculation that is not obvious from its picture.
Before comparing totals, check the following:
- Is the export using the exact same saved filter or JQL as the gadget?
- Does the gadget apply a project, date range, status, or other setting in addition to the filter?
- Are you comparing the same point in time? Issues may have changed after the dashboard loaded or while the export was being prepared.
- Do the dashboard viewer and exporter have the same issue permissions?
- Does the gadget show a limited number of results, or a grouped count rather than every matching issue?
For a chart, an exported list of issues may be the right source for rebuilding a chart in Excel, but it is not necessarily the same as exporting the chart’s rendered image or its computed values. Recreate the grouping in Excel only after confirming the gadget’s criteria. Otherwise, a pivot table or chart can produce a plausible-looking but inaccurate result.
When a CSV is not enough
If the requirement is to reproduce the dashboard’s appearance, a CSV is the wrong format. Take a screenshot or use an approved reporting or documentation process for a visual snapshot, bearing in mind that an image is not a data table and may become outdated immediately. If the requirement is to refresh data regularly, manually downloading a CSV may also be inconvenient.
For recurring reporting, consider these alternatives:
- Jira filters and Excel: keep the saved filter as the agreed source, then periodically export its results. This is straightforward for occasional reports.
- Marketplace apps: some Jira apps provide scheduled reports, spreadsheet exports, or dashboard-oriented reporting. Review the app’s supported Jira deployment, permissions, data handling, and licensing before relying on it.
- REST API or an integration: a developer can retrieve issue data and transform it into a workbook or data feed. This requires appropriate authentication, pagination, field selection, and attention to Jira’s API limits and access rules.
- Business intelligence tools: an approved connector may be more suitable for large or recurring cross-project analysis, but setup and licensing vary.
Automation does not remove the need to validate scope. A scheduled export can repeatedly deliver the wrong data if its query, access permissions, or field mapping is incorrect. For a one-off request, the built-in filter-and-CSV route is often simpler and easier to audit.
Permissions, privacy, and sharing
Exported files can be easier to copy, email, or store outside Jira than the original dashboard. Treat them according to the sensitivity of the issue data. Descriptions, comments, customer details, and other fields may contain information that should not be distributed broadly. Export only what the recipients need, store the workbook in an approved location, and follow your organization’s retention and sharing rules.
Also consider whether the saved filter or dashboard is shared with the intended audience. Sharing a workbook does not grant Jira access, and Jira access does not automatically protect a downloaded copy. If people need a current, permission-aware view, a shared Jira dashboard or filter may be a better choice than emailing snapshots of its data.
Frequently Asked Questions
Can I export a Jira dashboard directly to an .xlsx file?
Usually, no—not as a complete, editable Excel workbook that preserves all gadgets and their layout. Export the issues behind a gadget or filter as CSV, then open the file in Excel and save it as .xlsx. Available Jira options vary by version and installed apps.
How do I export only the issues shown in a Jira gadget?
Find the gadget’s saved filter or reproduce its search criteria in Jira issue search. Run that search, select the fields you need, and export the results as CSV. Check any gadget-specific date, project, or display limits before comparing the spreadsheet with the dashboard.
Does exporting Jira to CSV include charts and formatting?
No. CSV stores tabular text data; it does not preserve dashboard layout, chart styling, or Excel formatting. You can use the exported records to build a new chart in Excel, but you must reproduce the relevant grouping and criteria.
Why are some Jira issues missing from my export?
Check the filter criteria, gadget settings, and your Jira permissions. The export may also reflect a different time window or a later data refresh than the dashboard. A user generally cannot export issues they are not permitted to view.
Can Jira send dashboard data to Excel automatically?
Not as a universal built-in dashboard-to-workbook feature. For regular delivery, investigate an approved reporting app, API integration, or analytics connector. Confirm licensing, permissions, refresh behavior, and data protection before setting up automation.
Which method should you use?
For a one-time spreadsheet, use the Jira issue search behind the relevant gadget, export a focused CSV, verify the results, and save an .xlsx copy. For a visual snapshot, capture the dashboard separately rather than expecting Excel to reconstruct it. For scheduled or organization-wide reporting, evaluate a supported app, API integration, or analytics tool with your Jira administrator. Keeping the dashboard’s filter, export date, and field choices alongside the workbook makes the result far easier to interpret and trust.
Related
- Excel Table Data Sorting: Steps, Options, and Fixes
- Excel Spreadsheet Not Responding? Causes and Fixes
- Excel Suddenly Not Responding? Causes and Fixes
Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.
More in Charts & pivot tables
- Excel: Remove a Trendline From the Legend, Not the ChartTo remove a trendline from an Excel chart legend without removing the line, click the legend, click the…
- Excel: Hide Columns Without Affecting Your Chart ViewYes. In Excel for Microsoft 365 on Windows, select the chart, go to Chart Design > Select Data…
- Excel Logarithmic Scale Histogram: What WorksYes—but Excel’s built-in Histogram chart cannot put its horizontal category axis on a logarithmic scale. The practical workaround…
- Excel Combo Chart: How to Combine Bars and a Line in ExcelTo make a bar-and-line combo chart in Excel for Microsoft 365 on Windows, select your data, choose Insert…
- Line of Balance Graph: Meaning and How to Read It ClearlyA line of balance graph is a time-and-location chart used to plan and monitor work that repeats across…
- How to Copy a Graph in Excel: Steps and OptionsTo copy a graph (called a chart in Excel), click its outer border, press Ctrl+C, click where you…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.