How to reclaim Jira storage and boost performance by cleaning up zombie attachments

[#1]

Is your Jira Data Center instance feeling a bit... heavy? If your backup times are creeping up and your infrastructure team is constantly asking for more disk space, you likely have a "zombie attachment" problem.

In large Jira instances, years of accumulated screenshots, log files, and video recordings from closed tickets sit idle, consuming expensive storage and slowing down system maintenance.

Who this is for

• Primary Audience: Jira Admins and Infrastructure Leads.

• Environment: Jira Data Center.

• Marketplace Link: Issue Archiver & Attachment Housekeeper for Jira

---

The Native Jira Approach (and why it scales poorly)

By default, Jira keeps every attachment ever uploaded to an issue, regardless of whether that issue was closed five days or five years ago.

To reclaim space natively, admins usually have to:

1. Manually delete attachments: This is impossible at scale.

2. Delete entire projects: This is risky, as you lose the issue history and comments needed for audits.

3. Bulk Database/Filesystem scripts: These are dangerous, unsupported, and can lead to "missing file" errors and database inconsistencies.

The result? Most admins just keep buying more storage, leading to "storage bloat" that makes re-indexing and backups take hours (or days).

The Solution: Automated Housekeeping

Issue Archiver & Attachment Housekeeper allows you to define "Housekeeping Policies" that automatically strip unnecessary attachments from issues based on their age or status, while keeping the issue itself intact for record-keeping.

Step-by-step: Setting up your first cleanup policy

1. Define your "Retention Window"
Decide how long you actually need to keep files on active storage. For many teams, any attachment on a ticket closed more than 2 years ago is a "zombie"—it’s taking up space but will likely never be opened again.

2. Create a Housekeeping Policy
Navigate to the app's configuration and create a new policy. You can scope this to specific projects or the entire instance.

• Tip: Start with a "test" project to see the results before going global.

Define exactly which issues should be targeted for attachment removal based on JQL or status.

3. Enable "Soft Deletion" for Safety
The app supports a retention period for the "housekept" attachments. This means the files are moved to a temporary area before permanent deletion, giving you a safety net if a user suddenly realizes they need a specific file back.

4. Maintain the Audit Trail
One of the best features is that the app maintains metadata. Even after the file is gone, the issue history shows that an attachment existed, who uploaded it, and when it was removed by the Housekeeper.

Keep your audit trail intact even after the physical file is removed to save space.

The Proof: Real-world Impact

Imagine a Jira instance with 500GB of attachments. Typically, 40-60% of that data belongs to issues that haven't been touched in over two years.

• Before: 500GB storage, 4-hour backup window, sluggish re-indexing.

• After Housekeeping: 250GB storage (50% reduction), 2-hour backup window, significantly faster maintenance cycles.

By removing the "weight" of old files, you aren't just saving disk space; you are making your entire Jira environment more agile and easier to manage.

If you are planning on the migration to Jira Cloud, it is also an opportunity to unload the unnecessary baggage and avoid exceeding the storage limit.

Ready to declutter your Jira instance and stop paying for "zombie" storage?
Check out the user guide to learn more about the features and also additional resources.

Issue Archiver & Attachment Housekeeper for Jira | Atlassian Marketplace

Have questions about setting up your first policy? Drop a comment below and let’s discuss your storage strategy!