Import and export
Moving from another system: Cases → Import cases (editors). Supported:
- TestRail — CSV export (including “Steps (Step)” / “Steps (Expected Result)”) and XML export;
- Qase — the project’s JSON export and CSV;
- any CSV: columns are mapped to case fields right on the page (TestRail and Qase headers are recognized).
Before anything is written there is always a preview: how many cases will be created, updated, left unchanged,
which rows are skipped and why. Suites are created by path (Payments > Cards), and everything can go into a
separate top-level suite. The external ID (C101, QA-7) is remembered, so importing again updates cases
instead of breeding duplicates.
Export: the CSV and Excel links on the case list (the whole project or the current suite) and on a run
page (results). CSV is UTF-8 with a BOM; cells starting with =, +, -, @ are escaped against formulas.
API: POST /api/projects/:project/imports/cases (dryRun: true — preview only),
GET /api/projects/:project/exports/cases?format=csv|xlsx&suiteId=, GET /api/runs/:id/export?format=csv|xlsx.