Importing and moving data
The CSV importer, the Jira configuration card, and what each one really does.
Importing and moving data
The CSV importer (real)
/dashboard/integrations has a CSV bulk tasks card. It is the supported way to bring work in.
- Export your current board from Jira (or any tool) as CSV.
- Open /dashboard/integrations and select CSV bulk tasks.
- Choose the delimiter (comma, semicolon or pipe) and whether to skip invalid rows.
- Run the import. Rows are created through the task write path, so each imported task gets an id, timestamps and shows up in /dashboard/tasks immediately.
Column mapping follows the task fields: title, description, status, priority, story points, assignee, sprint, due date and tags.
The Jira card (configuration-only)
The Jira import card records a site URL and project key and lets you test the connection, but this build makes no call to Atlassian APIs. Treat it as configuration you can review, not as a sync. If you need data in now, use the CSV importer.
Other integration cards
- Slack: incoming webhook URL, channel and subscribed events.
- GitHub: repository URL, default branch and PR auto-linking.
- Google Calendar: internal calendar feed only — no Google sync happens in this build.
- Webhooks: an endpoint URL, an optional signing secret and the events to send.
- Zapier: a catch-hook URL and a trigger event.
Each card persists its configuration to your account preferences, supports a draft state you publish later, and can be tested from the same dialog.
Moving data out
Use GET /api/reports/export with format=csv or format=json for datasets, and the Data export card in /dashboard/settings for your own records.