My data team is looking to make some larger attachments to JIRA tickets. Specifically, we have batches of images that need uploading to the website and it would be convenient to be able to attach those batches as rar files to the respective request.
The possible downside here is that those files often get as large as a gigabite.
I'm wondering what the SPECIFIC speed or performance implications of storing gigabite attachments is. These attachments are going to range from 20mb to 1000mb and they'll be attached to tickets with near daily frequency.
When I say "specific" implications - I know that the database will be slower as it gets bigger. What I don't know is what sorta implications large attachments have in things like issue search and updating of issue fields, etc. In addition to this, I'm not sure when attachments get archived or compressed on the backend.
If you could get me whatever information you can, it would be appreciated.
Jira is not designed for large file handling and you'll find large files fail to upload or download reliably. If you are successful in storing them, you won't find any impact on the system - the files sit on a file system as a block of data and are only used when someone tries to view them.
However. You say you are on Cloud. Where there is a 25Gb limit for smaller sites, and 100Gb for larger ones.This idea is a non-starter. You should look to provision a proper large file store system and link Jira issue to it.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs