CSV import and export

Export tasks to CSV. Import via a staged review-then-commit flow so a malformed row never half-updates your project.

CSV is the universal "move tasks in or out" format. Export is one click. Import goes through a staged review, so you never half-update a project with a malformed file.

Available on every tier.

Exporting

From the project's Tasks page, open the export menu (toolbar) and choose CSV export. Frostbyte produces a CSV with one row per task and columns:

  • id, title, description, type, priority, status
  • area (name), release (name), assignee (email)
  • createdAt, updatedAt, subtasks (semicolon-delimited list of titles)

The export reflects the current view's filter, if you're filtered to "Bugs only", you get bugs only. To export everything, switch to the All filter first.

Subtasks are flattened into one cell per task. Activity entries and Feedback Hub submissions are not included; this is a tasks-only export.

Importing via staged review

Import goes through a two-step flow:

  1. Upload the CSV. Frostbyte parses it and creates a temporary CsvImportSession record (TTL 24 hours).
  2. Review the parsed rows on a staging page. Each row shows what would be created/updated, with errors flagged inline.
  3. Commit the import. Only on confirm does Frostbyte write rows to the project.

This means a CSV with a bad column name doesn't half-update; nothing changes until you commit, and you can discard the staging session at any point.

Required columns

For new tasks, the import accepts:

  • title (required)
  • description, type, priority, status, area, release, assignee, all optional.

For updates to existing tasks, include id. Rows with an id matching an existing task in the project trigger an update; rows without id create new tasks.

area and release are matched by name. If the named area or release doesn't exist, the row is flagged as needing manual selection during review.

What gets validated

The staging page surfaces:

  • Missing required fields (title).
  • Invalid enum values (type must be feature/bug/improvement; status must be todo/in-progress/done).
  • Unknown areas or releases (you can map them to existing ones, create them, or leave the row partial).
  • Active-task limit overruns, if importing N rows would exceed your plan's active-task cap, the import is blocked. See Plans and limits.

Discarding

Click Discard staging to throw away the parsed session. Nothing was written; nothing needs to be undone.

Unconfirmed sessions auto-expire after 24 hours.

What's next

Last updated