Privacy-safe Jira CSV tool

Jira sprint carryover analyzer

Load a Jira CSV and measure how many issues appear in multiple sprints, how many remain open and how old carried work is. The file stays in your browser.

CSV contents are processed only on this device and are never sent to our server.

Choose Jira CSV

For best results use Jira “Export CSV — all fields” with Issue key, Summary, Status, Status Category, Created and repeated Sprint columns. Up to 50,000 issues / 10 MB.

Download sample CSV

Statuses that mean done

When Status Category is present, Jira’s Done category takes precedence. The list recognizes localized/custom completed categories and is the fallback when the category is missing; separate names with commas.

How the calculation works

Jira CSV commonly repeats the Sprint column when an issue belonged to several sprints. The tool merges duplicate issue keys and counts distinct non-empty Sprint values per issue. The carryover proxy is issues in multiple sprints divided by issues with at least one sprint. It is not perfect history: reopened issues, renamed sprints and incomplete exports can change the result.

What to do with the result

Review open issues that have appeared in the most sprints.
Separate dependencies and scope change from poor estimation or oversized work.
Do not rewrite original story points; estimate remaining work for planning.
Track the trend by sprint and never use one percentage to rate individuals.

Read the guide and methodology Open Jira migration readiness