Attachment storage outside JIRA

[Mikus Strazdins]

We currently use JIRA in several business processes. These processes result in the creation of documents that are attached to JIRA as attachments. As a result, JIRA's available memory is rapidly being filled up and the available memory needs to be increased all the time (now we have more than 1 Tb located in JIRA). As we know JIRA is not meant to be a file storage site, but we need to store files added to JIRA during the process for later access, so do you have experience managing attached files? 

Maybe there are some solutionts to move all existing attachments to ondrive or s3 and save a link to the new file location in the application?

[JimmyVanAU · Accepted solution]

Hi Mikus,

Glad to hear that your business teams are using Jira in anger. It's best to review the process with which teams are creating/generating the attachments, and also to look at whatever tools your team are using - Dropbox, Onedrive or Google Drive, and seeing if links to attachments can be used instead of actual files.

If the teams are using a mixture of solutions, or it's something that you want full control over (and not say, the G Suite admin), you might like to check out the following apps:

https://marketplace.atlassian.com/apps/1219492/project-s3-documents-for-jira?hosting=server&tab=overview

https://marketplace.atlassian.com/apps/1213711/amazon-s3-connector-for-jira?hosting=server&tab=overview

Which do as you suggest and allow you to use S3 as the storage location.

Hope that helps :)