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 a malformed file never half-updates a project.

Available on every tier.

Exporting

From the project's Tasks page, open the export menu in the 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; switch to the All filter to export everything.

Subtasks are flattened into one cell per task. Activity entries and Feedback Portal submissions aren't included; this is a tasks-only export.

Importing via staged review

Import is a three-step flow:

  1. Upload the CSV. Frostbyte parses it into a staging session.
  2. Review the parsed rows on a staging page. Each row shows what would be created or updated, with errors flagged inline.
  3. Commit the import. Only on confirm does Frostbyte write anything to the project.

A CSV with a bad column name can't half-apply. 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 trigger an update; rows without one create new tasks.

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

What gets validated

The staging page surfaces:

  • Missing required fields (title).
  • Invalid values (type must be feature, bug, or improvement; status must be todo, in-progress, or 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 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, so nothing needs undoing. Unconfirmed sessions expire on their own after 24 hours.

What's next

  • For a visual export of the board: PDF export.
  • For programmatic task management without CSV: MCP server.
Last updated