CSV export

Download the current filtered ticket list as CSV.

The ticket inbox has an ⬇ Export CSV button next to + New ticket. Clicking it downloads exactly what's currently visible — same filters, same sort.

What's in the file

Each row is one ticket with these columns:

reference, subject, status, priority, source, category,
requester_name, requester_email, assigned_to,
created_at, updated_at, first_response_at, resolved_at, closed_at,
csat_rating, csat_comment, csat_rated_at

Timestamps are ISO 8601 (2026-05-19T14:32:00+00:00). Empty cells mean the value hasn't been set — unresolved tickets have no resolved_at, unrated tickets have no csat_rating. See Customer feedback for what csat_* means.

Filters honored

Whatever filters are active in the URL apply to the export:

  • Status?status=open exports open tickets only. ?status=resolved for resolved. ?status=all exports everything regardless of status (escape hatch — UI doesn't expose this but the URL does).
  • Assignee me?assignee=me exports just your tickets.
  • Priority?priority=high.
  • Category?category_id=….
  • Search query?q=login exports tickets matching "login" in subject or reference.

Stack as many as you need. The exporter respects all of them.

Streaming, not loading

The export streams to your browser as the data comes off the database, in chunks of 500. A workspace with 100 000 tickets exports in 10 seconds without OOM-ing the server. Open the URL in a tab and your browser starts saving immediately.

UTF-8 with BOM

We prepend a UTF-8 byte-order mark so Excel correctly renders diacritics in subject lines and customer names. Other tools (Numbers, LibreOffice, jq) ignore the BOM.

What's not in the export

  • Reply / note content — only the ticket itself. If you need conversations, that's a future feature.
  • Internal notes (irrelevant since replies aren't exported either).
  • Tags (planned).
  • Custom fields (not yet a feature).

What you might do with it

  • Quarterly board report on ticket volume per category.
  • Audit log of every ticket from a specific customer.
  • Feed into a BI tool for cross-product analysis.
  • Migrate to another platform (we won't be offended).