File storage

Choose where uploaded files go — built-in storage or your own cloud bucket.

Settings → File storage

Where uploaded files go — issue attachments, comment images, anything else uploaded through the app. One provider at a time for the whole organization. Owner/Admin only.

How it works

Every provider except Local storage namespaces uploads under a Path prefix — leave it blank to use the default shown on the page (based on your workspace slug) so uploads from different organizations sharing one bucket never collide.

Test writes and reads a small file using whatever's currently in the form (even before saving) — always run it after entering credentials, before saving, so a typo doesn't silently break every upload for the whole org.

Provider setup

Stores files on the backend container/host's own disk — no external account needed.

  • Local path — a folder path on the backend container. Use a mounted Docker volume in production, or files vanish on redeploy.
Fine for local development. In a multi-instance or ephemeral-container deployment, files written to one instance won't be visible from another — use a real object storage provider instead.
Switching providers does not migrate existing files — anything already uploaded stays wherever it was, and only new uploads go to the new provider. Old attachment links can break if you also delete the original bucket/folder.