Feature request: project-scoped portable export with tasks, comments, attachments, and relations

[shrishailrana-maker]

Pre-submission checklist

• I searched open and closed issues for single-project export, portable project backup, and bulk task export.

Problem

Migrating or backing up one project currently requires clients to enumerate tasks and then query comments, attachments, and relation details per task.

A measured 47-task project export with comments, attachments, and relations required at least 142 task-related API requests in the client (one task collection plus three per-task read families) and took about 2.2 seconds on a local network. Larger projects multiply this cost and are more likely to fail partway through.

The existing v2.4.0 API exposes user-wide export routes, but no project-scoped export route.

Requested behavior

Please provide a project-scoped portable export, either synchronously for small projects or as an asynchronous export job:

1. Export project metadata and every visible task.
2. Optionally include comments, relations, labels, assignees, and attachment metadata/files.
3. Return a machine-readable manifest with schema/version information.
4. Preserve task identifiers and relation identities.
5. Stream or archive binary attachments instead of embedding base64 in JSON.
6. Apply normal project permissions.
7. Make partial/truncated export impossible or explicitly reported.

Why this belongs in the server

The server can read a consistent project snapshot efficiently and can package attachments without an N+1 API crawl. This helps backups, migrations, support bundles, and integrations.

Version

Measured against the v2.4.0 API.