nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Very urgent, Storage

Waranya Assawachainarong

Very urgent, right now my storage is almost full.
1. I would like to know if the storage is full, will users be able to create issues and attach files?
2. When storage is full, what should I do? What if I don't want to upgrade storage?
3. Will old data be lost?

Accepted answers

All comments

John Funk

Hi Waranya - Welcome to the Atlassian Community!

You would need to delete some of the attachments on some of your issues that are large files. Not sure exactly what will happen when you run out of storage, but there's a good case you might not be able to add issues. Almost for sure you would not be able to add more attachments.

There are some Atlassian Marketplace apps that can help with the storage (meaning an extra cost). Also, there is one app called Revyz Configuration Manager for Jira (for which I am an advisor) that should be able to help show you the issues with the highest storage impact. You can install the app on a trial basis for 30 days and get your data cleaned up during that time.

Waranya Assawachainarong

Can I have a definite answer? Whether users will be able to create issues or not? Because it will greatly affect the company.

John Funk

See this previous post that might help with your answer.

Waranya Assawachainarong

Not sure exactly what will happen when you run out of storage, but there's a good case you might not be able to add issues. <<< I don't understand this one. This means that users will not be able to create issues, is that correct?

Nic Brough -Adaptavist-

Hi Waranya,

On a server/DC system, your storage limit is the physical size of the disks you have on the server. If you fill up the disk with the Jira home directory on it, then Jira will no longer be able to accept new or amended attachments, and will start to have problems working as the index and temporary workfiles will not be writeable. Similarly for the disk the Jira install is on (again, no working space), and the disk the database is held on (it won't be able to add or edit issues)

On Cloud, the storage limit is not an absolute, it is a guide. It does include the space needed for the installation and working files, but it is not limited like a physical disk is.

If you exceed the storage limit, nothing will stop working and you will not lose anything, but you will start getting warnings from Atlassian that you have exceeded your allowance. If you continue to exceed the storage limit for your licence tier, you will eventually be moved up to a higher tier of usage, one that includes a higher storage limit.

Kārlis Rozenbergs

If you’re on Jira Cloud Standard, the 250 GB storage cap can get tight mostly due to attachments. Before upgrading, a quick win is removing exact duplicate attachments and low‑value files (logs, dumps, temp).

Attachment Architect scans Jira, groups files by SHA‑256 hash, flags large/old files, and supports safe bulk deletions with audit logging.

Marketplace: https://marketplace.atlassian.com/apps/2464899201/attachment-architect?utm_source=community&utm_medium=organic&utm_campaign=attachments_storage_standard

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud