Move Jira issues to GitHub Issues
Drop a Jira exportCSV, up to 1,000 issues
Nothing converted yet.
Export from Jira
- 1In Jira, open Filters and choose Search work items (or open your project's list view).
- 2Search the project, or pick a saved filter, so the list shows the issues you want to move.
- 3Select Export, then Export Excel CSV (all fields). Pick all fields, not current fields: current fields drops comments and custom fields.
- 4Drop the downloaded .csv file above.
Import into GitHub Issues
- 1Select Continue in importer above, or open the CSV to GitHub Issues importer and drop the downloaded CSV.
- 2Sign in with GitHub and pick the repository.
- 3Match Jira people to GitHub logins, then import.
Field mapping
| Jira | GitHub Issues | What changes |
|---|---|---|
| Summary | Title | Unchanged. |
| Issue key | Dedupe marker | Unchanged. |
| Description | Body | Converted by a rule specific to Jira. |
| Created | Created date | Dates become ISO timestamps. |
| Updated | Updated date | Dates become ISO timestamps. |
| Resolved | Closed date | Dates become ISO timestamps. |
| Resolved, Resolution, Status Category | State | Converted by a rule specific to Jira. |
| Assignee | Assignee | Unchanged. |
| Labels | Labels | Unchanged. |
| Issue Type | Labels | Converted by a rule specific to Jira. |
| Priority | Labels | Converted by a rule specific to Jira. |
| Component/s | Labels | Converted by a rule specific to Jira. |
| Fix versions | Milestone | Unchanged. |
| Comment | Comments | Converted by a rule specific to Jira. |
| Attachment files (names and links go in the footer; opening them needs a Jira login) | Not moved | Stays in Jira. |
| Inline images | Not moved | Stays in Jira. |
| Rank and board order | Not moved | Stays in Jira. |
| Workflow history, work logs and watchers as people | Not moved | Stays in Jira. |
| Issue keys (GitHub numbers the issues again; the Jira key stays in the footer) | Not moved | Stays in Jira. |
| Parent and child links as GitHub sub-issues (the parent shows in the footer) | Not moved | Stays in Jira. |
| Fix versions after the first as milestones (they go in the footer) | Not moved | Stays in Jira. |
FAQ
Does my Jira export leave my browser?
No. The file is read and converted in your browser, and nothing is uploaded. The rows go to a server only if you continue into the importer and pick a repository, and then they go straight to GitHub. We keep no copy.
Are comments and attachments moved?
Comments are. Each one becomes a GitHub comment with its Jira author and date, and its wiki markup converted to Markdown. Attachment files are not: Jira exports only their names and links, and opening a link needs a Jira login. The names and links are written at the end of the issue.
What happens to sub-tasks and parent issues?
A sub-task becomes an ordinary issue labelled sub-task. Its parent is not linked as a GitHub sub-issue. The parent's id and title are written at the end of the issue, so you can find them again.
What about more than 1,000 issues?
The importer takes 1,000 issues at a time. A larger export converts here, with a warning that shows the count. Split the Jira search into batches, for example by created date, and move each file in turn.
How are Jira types, priorities and components mapped?
A Bug becomes the bug label. A Story, Improvement or New Feature becomes enhancement. Any other type becomes its lower-case name, such as epic or task. Priority becomes a label like "priority: High" and each component a label like "component: Checkout". The first fix version becomes the milestone.
Why do dates need a format and time zone?
Jira writes dates without a time zone, in the format set for your site, such as 31/May/23 12:08 PM. The converter detects the format from your file and lets you change it. Pick the time zone your Jira site shows, so created and closed dates land at the right hour.
Run your new GitHub issues in Gitsu.
Try Gitsu free