A Jira administrator chooses where client files are kept, on the Collectly plan and storage admin page (Jira settings → Apps), section File storage. The choice applies to new requests; each request keeps the storage it was created with.
| Storage | Max file size | Plans |
|---|---|---|
| Collectly storage (default) | 1 GB | Paid plans and trial |
| Your own bucket: Google Cloud Storage, Amazon S3 or S3-compatible (Cloudflare R2, Wasabi, MinIO), Azure Blob Storage | 1 GB | Every plan |
| Jira attachments | 25 MB | Every plan |
Collectly storage is managed by Collectly, encrypted and linked from the issue, so files do not use your Jira storage. Nothing to set up.
Your own bucket: files go straight from the client to your storage; agents download them from the issue.
Jira attachments: files are attached to the issue. On the free plan this is what new requests use unless you connect your own bucket.
https://collectly.cloud with methods PUT and GET. The form's How to prepare the bucket section has the exact steps for each provider.Use Test connection to check it later. Disconnect switches new requests back to Collectly storage; files of earlier requests stay in your bucket but cannot be downloaded through Collectly until the same bucket is connected again.