Reports & data export
Saved report schedules, run history, and CSV/JSON downloads.
Reports & data export
Report schedules
/dashboard/reports lets you build a report and keep it. A schedule is a dataset, a range in days, a grouping, a cadence and a recipient list. Schedules are full CRUD through /api/reports and /api/reports/<id>, and creating one notifies the owner.
Datasets
The registry comes from GET /api/reports, so the builder never hardcodes a list:
- tasks — group by status, priority, assignee or sprint. Values are tasks.
- sprints — group by status. Values are sprints.
- team — group by member or department. Values are open tasks.
- wellbeing — group by mood or day. Values are check-ins.
Running and previewing
- POST /api/reports/preview renders the report without saving it — use this while building.
- POST /api/reports/<id>/run executes a saved schedule immediately and records a run.
- GET /api/reports returns schedules plus the 50 most recent runs, each with a status and timestamp.
Exporting
GET /api/reports/export?dataset=tasks&rangeDays=30&groupBy=status&format=csv returns a file attachment. format=json returns the same rows as JSON. Every parameter is validated against the registry, so an unknown dataset or grouping is a 400 rather than an empty file.
Other ways data leaves the app
- The Data export card in /dashboard/settings for your own records.
- The CSV bulk tasks integration card in /dashboard/integrations for board-shaped exports and imports.
- Any list endpoint with a large pageSize, if you want to transform the JSON yourself.
Recipients
Recipients are member ids. When a scheduled run completes they receive a notification with a link back to the report, which is how a weekly digest reaches people who never open the dashboard.