Skip to content

Docs

Import from Jira or CSV

Bring tickets from Jira with their comments, history, logged work and attachments, or from any CSV file.

From Jira, directly

  1. An admin connects Jira under Workspace settings → Integrations: the Jira address (https://your-team.atlassian.net), the email of an Atlassian account that can browse the projects, and an API token of that account. Test connection reads the account.
  2. In a project, open Project settings → Import from Jira. Pick a Jira project or enter a JQL search, choose what to include, and Read from Jira.
  3. The preview shows the counts, how Jira people were matched, and how statuses map. Change any of it, then import.

What comes along:

  • Tickets with their creation, update and resolution dates, reporter, assignee, parent (epics, stories, subtasks), priority, labels, story points, original estimate, start and due date, and the description (Jira’s rich text becomes Markdown).
  • Statuses map by name, then by Jira’s status category. Done with a resolution such as Won’t Do or Duplicate becomes Cancelled.
  • Comments with author and date, and the change history: status changes become normal status history, so flow and cycle-time charts include them.
  • Logged work (admins only, off by default) becomes time entries for matched people. Entries in closed months, of unmatched people, or over 24 hours on one day are left out and counted.
  • Attachments up to 25 MB, with their uploader and date.

Comments, change history and logged work come with the import on Pro and Business; on Free the import brings the tickets.

People are matched by email, then by a unique name. Unmatched people keep their Jira name on comments and history, and their tickets stay unassigned.

Running it again only adds what is new, so import early and once more on the day you switch. Ticket numbers are new; each ticket shows “Imported from Jira as KEY-123” with a link back. Nothing is ever written to Jira, imports notify nobody, and the Jira token stays on the server.

From a CSV file

Project settings → Import tickets reads a CSV, for example a Jira export (Issues → Export → CSV), on every plan. It shows a preview and imports everything or nothing, up to 2,000 tickets at a time.

Recognised columns: Summary or Title (required), Issue key, Issue Type, Parent or Parent id, Status, Priority, Description, Story Points, Original Estimate, Labels, Assignee (matched by email or name) and Due Date. Types such as Change, Change request and CR become change requests in client projects.

Then make them agent-ready

Imported stories score like any other ticket. Open one and choose Write with Nova: the old acceptance criteria become checks, and whatever the story never said becomes a question.