Jira issues to dashboard
Jira issues, without fighting the export first.
Run a JQL search in Jira, export the results as CSV, and drop the file here. Three things about that file need handling and all three happen on load: the dates arrive as dd/MMM/yy HH:mm rather than ISO, multi-value fields like Sprint and Labels are emitted as several columns that all share one header name, and Status Category is the stable grouping while Status itself is whatever your workflow happens to call things.
Prefer the full explorer? Open the app, or start from the generic dashboard builder.
Two exports, two completely different files
Jira offers you a choice at export time between current fields and all fields, and the two produce files so different that scripts written against one break instantly on the other. Current fields gives you roughly the columns visible in your issue navigator. All fields gives you every custom field anyone has ever added to the instance, which on a mature Jira can mean two hundred columns, most of them empty, several of them named things like Customfield_10024. Neither is wrong. You just have to pick one and stay with it.
The other thing to check before you celebrate is the row count. The CSV export is capped at a thousand issues by default, and Jira applies that cap quietly. A JQL query matching four thousand issues hands you a file of one thousand with no banner, no warning and no indication which thousand you got. If your export is exactly 1000 data rows, assume it is truncated rather than coincidental, and narrow the query.
How to export from Jira
- Search for the issues you want Open Issues, then Search for issues, and write JQL rather than clicking filters. Something like project = ENG AND created >= -90d gives you a defensible scope instead of whatever the last person left in the box.
- Check the result count first The header above the results tells you how many issues matched. If it is over a thousand, split the query by month or by component now, because the export will silently truncate rather than warn you.
- Export as CSV The Export button is at the top right. Choose CSV (all fields) for a full picture or CSV (current fields) for a manageable one. All fields is safer if you are not sure which custom field holds your points.
- Open the header row and look at it Confirm which column carries story points, since that name varies by instance, and note how many columns share the name Sprint. Both are normal and both are handled here.
- Drop the CSV on this page Status Category becomes the default grouping, the repeated Sprint columns collapse into one, and the dd/MMM/yy timestamps become a usable time axis.
The thousand-row cap is an instance setting on Jira Data Center and Server, so an administrator can raise it. On Jira Cloud you are better off splitting the JQL by date range and merging the files afterward.
Try with sample Jira data (the same columns, 104 rows, no upload needed).
What the dashboard shows
Every panel below is built from a column that is actually in the export, named the way Jira names it.
- Throughput by sprint. Issues resolved per Sprint value, with the repeated columns merged so an issue carried across three sprints appears in all three rather than in none.
- Status Category flow. To Do, In Progress and Done as the top-level split, because those three are stable across every workflow while Status names are not.
- Cycle time from Created to Resolved. Both timestamps are in the file, parsed out of Jira's format, so the elapsed time per issue is available without touching the changelog.
- Story point burn. The points column is detected whatever it is called on your instance, and summed per sprint alongside the issue count.
- Issue Type mix. Story, Bug, Task and Sub-task as shares, which is the quickest read on how much of a quarter went to unplanned work.
- Assignee and Component load. Two group-bys that cross-filter, so you can see which person is carrying which part of the codebase.
Issue key,Issue id,Issue Type,Summary,Status,Status Category,Priority,Resolution,Assignee,Reporter,Story Points,Sprint,Created,Updated,Resolved,Labels,ComponentsSix Jira export behaviors worth knowing before you report
- A silent thousand-row cap. The default export limit truncates without telling you. An export of exactly 1000 rows is almost never a coincidence, and every percentage computed on it is biased toward whichever thousand Jira returned first.
- Dates are dd/MMM/yy HH:mm. Written as 14/Mar/26 09:41 rather than anything ISO. Spreadsheets in a non-English locale fail on the month abbreviation entirely, and the two-digit year is its own small landmine.
- Multi-value fields become repeated columns. An issue in three sprints produces three columns all headed Sprint. Most parsers keep the last one and drop the rest, so two thirds of your sprint history vanishes without an error message.
- Story Points is a custom field. Its column name depends on how your instance was configured. It might be Story Points, Story point estimate, or a raw custom field id, so a hardcoded column name is a script that works on one Jira.
- Status is workflow-specific, Status Category is not. One team's In Review and another's Code Review are the same phase with different labels. Status Category collapses everything into three values that mean the same thing everywhere.
- Current fields and all fields differ enormously. The same query exported two ways gives you fifteen columns or two hundred. Pick one and write your process around it, because the two are not interchangeable.
Jira's export is unusually honest about its own complexity: it gives you the real shape of a configurable system rather than a tidied summary. Once repeated columns are merged and Status Category is doing the grouping, the file supports better delivery questions than most trackers can answer at all.
Frequently asked questions
Why does my Jira export stop at 1000 rows?
That is the default export limit, and Jira applies it without a warning banner. Your JQL might match four thousand issues while the file holds one thousand, which quietly biases every metric you compute. On Server and Data Center an administrator can raise the cap. On Cloud, split the query by date range, export each slice, and merge the files before loading them here.
How do I handle the dd/MMM/yy date format?
Jira writes timestamps as 14/Mar/26 09:41, which is neither ISO nor a format most spreadsheets guess correctly. A machine running a non-English locale often fails on the month abbreviation and leaves the whole column as text. This page recognizes the pattern explicitly, including the two-digit year, and turns Created, Updated and Resolved into real timestamps you can put on an axis.
Why are there several columns called Sprint?
Because Sprint is a multi-value field and the CSV export writes one column per value, all sharing the same header name. An issue carried across three sprints gets three Sprint columns. Most CSV readers keep only the last column with a given name and discard the others, which silently loses history. The parser here collects every column with that name into a single list per issue.
Should I group by Status or Status Category?
Status Category for anything you want to compare across teams. It has three values, To Do, In Progress and Done, and every workflow maps into them regardless of what the individual steps are named. Status is more precise within one team's process and useless across several, since one board's In Review and another's Awaiting QA describe the same phase.
Which column holds my story points?
It depends on your instance. Story Points is a custom field, so its exported name varies between Story Points, Story point estimate, and a raw customfield identifier, depending on how and when your Jira was set up. This page looks for numeric columns whose names resemble a points field and lets you confirm the choice, rather than assuming a name that only works on one deployment.
Is the issue data uploaded anywhere?
No. The file is parsed inside your browser tab and the charts are drawn from memory. Jira summaries and descriptions routinely contain customer names, security findings and unreleased plans, which makes this one of the worse files to paste into an unknown online converter. There is no server here to receive it and no account to create first.
Related tools
Open a Jira dashboard without touching a filter
104 issues with real Jira column names, dd/MMM/yy timestamps, a story points field, and issues that span more than one sprint. Load it and watch Status Category do the grouping.
Open the sample Jira dashboard