CSV Import

When you need to load a batch of issues all at once — migrating from another tool, pulling in a spreadsheet from a stakeholder, or seeding a new project — Fox's CSV import is the right tool. You can import tens, hundreds, or thousands of issues from a single file, with automatic column mapping and a preview step before anything lands in the project.

What You Need

A CSV file with at least one column: title. That's the only required field. Every other column is optional — Fox will fill in the rest with defaults or leave them empty.

Common columns Fox recognizes automatically:

title
type (matched against the project's issue types)
priority (matched by name)
status (matched against the project's statuses)
tags (comma- or semicolon-separated)
notes / description
due_date
estimate
resolution

Column names don't need to match exactly — Fox does its best to recognize variants — but if a column isn't picked up automatically, you can map it manually in the preview step.

Starting an Import

Mac — File → Import, then pick your CSV file
iOS / iPadOS — Project dashboard menu, then Import

Fox opens the import preview with your CSV parsed and columns mapped.

The Preview Step

Before anything is imported, you get a chance to:

Check column mapping — See which CSV column maps to which Fox field. Change any that aren't right.
Spot-check rows — Preview the first several rows as they'd appear after import.
Fix problems — Blank titles, unknown types, mismatched priorities. Fox surfaces what's wrong so you can fix it in the CSV and try again.

Only commit the import after the preview looks right. There's no "undo all" for an import, so getting the preview clean saves time.

Project-Specific Attributes

Priorities, types, statuses, and resolutions are matched against the target project's attributes by name. If your CSV has priority: Urgent but the project only has High / Medium / Low, Urgent won't map — either add the priority to the project first, or update the CSV.

Tags are more forgiving: any tag that doesn't already exist in the project can be created on import.

Tips

Start with a small test file — Import 5–10 rows first to verify your mapping works before running the full file.
Use UTF-8 — Save your CSV as UTF-8 to avoid encoding issues with accented characters, emoji, or non-Latin scripts.
Quote fields with commas — Standard CSV quoting rules apply. If your title contains a comma, wrap it in double quotes.
Match your project's attributes first — If you're migrating from another tool with different statuses or priorities, configure the new project's attributes before importing so the mapping works on the first try.

Alternatives

For situations where CSV isn't the right tool:

One-off issues — Just create them in Fox directly
Programmatic creation from other apps — Use Shortcuts
AI-assisted import — Ask an MCP-connected AI to create issues one at a time with the MCP Server