# Import issues from Jira

Teamhood imports Jira issues from the CSV file that Jira exports. Export it with all fields: an export with **my defaults** leaves out each issue's parent.

## Export the issues from Jira

1. In Jira, open the issue search and run a search that finds the issues to move, such as `project = ABC`.
2. Open the **More actions** menu, then **Export**.
3. Choose **Excel CSV - all fields** or **CSV - all fields**. Both give the same file.

## Import the CSV file

1. Select **+** at the top of the sidebar, then **Import**.
2. Drop the `.csv` file, or select the drop area to pick the file. The import recognises a Jira export by its **Issue key**, **Issue id**, **Summary** and **Issue Type** columns.
3. On **Placement**, check the types under **Types from a column**. Each Jira issue type becomes the Teamhood type next to it:
   - An Epic becomes a type whose items open onto their children, such as Project, when the place you import into allows one.
   - A Bug becomes an Issue, and a Story, Task or Sub-task becomes a Task, when your organization has those types.
   - A type of the same name wins, so a Bug becomes a Bug when your organization has a Bug type.
   - Any other issue type becomes the type under **Other items become**.
4. On **Map fields**, keep the **Issue key** column mapped. A first import maps it to a new text field named Jira key, when your role may create fields. A later import can match items by it.
5. On **Review**, select the import button. It names how many items the import creates.

## What is left out

- Comments, attachments, watchers and work logs.
- Created, updated and resolved dates. Teamhood keeps its own.
- Issue links other than **blocks**, such as **relates to** and **duplicates**.
- Remaining estimate, time spent, and the totals Jira adds up from sub-tasks.
- Jira's own fields such as **Rank**, and any column with no value.

## What works differently from Jira

- An issue becomes an item. Its parent, from the **Parent** column or the older **Epic Link** column, becomes its parent item.
- An issue that blocks another becomes its predecessor, a finish-to-start dependency.
- A status goes to the **Status** option of the same name. Otherwise To Do becomes New, Done becomes Completed, and In Review becomes Review, when your **Status** field has those options and every issue with that status may hold them. Any other status goes by its Jira category: to do, in progress or done. So does a status whose option one of its issues may not hold, for all of its issues.
- Assignees are matched to people by name, because Jira's export holds no email addresses.
- Labels become tags, when your organization has a **Tags** field. The original estimate comes in hours. The due date becomes **Finish** and the start date becomes **Start**.
- A description keeps its headings, lists, links, code and tables. A mention becomes the person's name, and an image becomes its file name.
- A custom field keeps its own name, such as **Story Points** for `Custom field (Story Points)`. Map it to a field on **Map fields**, or create one.

## Importing again

> **Importing the issues again without matching creates them a second time.** To update them instead, select **Update matching items** on **Map fields**. The import then matches each issue by its Jira key.

An issue whose parent is not in the file comes in at the place you import into.

## Next

- [How re-importing a plan works](../re-importing-a-plan/)
- [Import items from a CSV file](../import-items-from-a-csv-file/)
