# Trackwell Jira CSV Import

> Turn a Jira CSV export into a Trackwell project: issues, statuses, sprints, people. Reads the CSV file Jira exports for a filter (all fields) and maps it to a Trackwell project file: issue types, statuses with their category, priorities, assignees and reporters, labels, components, fix versions, sprints, story points, estimates, time spent, parents, links, comments and custom fields. It reports exactly what was mapped and what was left out.

Part of usefulweb.app (https://usefulweb.app/). Part of [Trackwell](https://trackwell.usefulweb.app/) (ownerApp: trackwell). Results are deterministic calculations from the inputs and the listed assumptions; the API returns exactly what the web page shows.

## Use it
- Human interface: https://trackwelljiracsvimport.usefulweb.app/ (interactive tool at https://trackwelljiracsvimport.usefulweb.app/tool)
- JSON API: POST https://trackwelljiracsvimport.usefulweb.app/api/v1/calculate with a JSON object of inputs (schema: https://trackwelljiracsvimport.usefulweb.app/api/v1/tool)
- OpenAPI: https://trackwelljiracsvimport.usefulweb.app/openapi.json
- MCP (Streamable HTTP): https://trackwelljiracsvimport.usefulweb.app/mcp - tool `trackwell_jira_csv_import`

## Inputs
- csv (textarea): Jira CSV export - In Jira: Filters → search → Export → Export Excel CSV (all fields). Paste it here or upload the file.
- csvFile (file): CSV file (optional) - Used instead of the pasted text when given.
- key (text): Project key (optional) - Empty = taken from the issue keys.
- name (text): Project name (optional)
- mode (select): Board

## Method
- Columns are found by their Jira header names; repeated columns (Labels, Component/s, Fix Version/s, Sprint, Comment, Watchers) are all read. Trackwell’s own CSV export uses the same names, so it reads back the same way.
- Issue types: Bug, Story, Epic, Sub-task, Incident (also Problem) and requests (Service request, IT help, Access, Support, Question) map to Trackwell types; everything else becomes Task. Priorities: Blocker/Critical → Highest, Major → High, Minor → Low, Trivial → Lowest.
- Each distinct status becomes a workflow status; its category comes from the “Status Category” column, else from the name (Done/Closed/Resolved → done; In Progress/Review/Testing/Waiting → in progress). The imported workflow allows every move; refine it in the workflow editor.
- Sprints: an issue’s last Sprint column is its current sprint; sprints that were followed by another one are closed, the open sprint with the most open issues becomes active. Story points come from “Custom field (Story Points)” or “(Story point estimate)”; Original Estimate and Time Spent are seconds in Jira and become minutes. Other “Custom field (…)” columns become text or number fields.
- Dates in Jira’s default format (24/Nov/26 9:15 AM) or ISO are read as UTC. Parents are found by “Parent id”/“Parent” (Jira issue id or key); “Inward/Outward issue link (…)” columns become links between imported issues. Comments keep author and time; Jira wiki markup (h2., *bold*, {code}) becomes Markdown.

## Limits
- Jira is a trademark of Atlassian. Trackwell reads the export file you provide; it does not connect to Jira. Attachments, work log details and change history are not part of Jira’s CSV export.