Introducing SBAM: Solving bulk attachments, email signature junk, and accidental deletions in Forge

[Patryk_Curiosity]

Hi App Central,

Managing attachments in Jira Cloud often feels like fighting the platform—from large unstructured ZIP archives to JSM tickets buried under dozens of Outlook signature logos.

I’m a software developer and the founder of Curiosity. Coming from a background in web application development, I’ve recently been focused on building lightweight, zero-maintenance tools for Jira Cloud natively on Atlassian Forge.

When analyzing Jira's file management workflows and testing existing Marketplace apps, three common operational bottlenecks stood out:

• The JSM Email Signature Graveyard: Every customer reply from email imports embedded social icons, tracking pixels, and company logos (<20 KB). Over time, tickets turn into messy galleries of useless PNGs, burying actual customer documentation.

• The Lack of Granular Bulk File Operations: Jira provides no native way to filter, audit, or bulk-manage attachments across issues. When admins need to reclaim storage or purge outdated files, they are stuck manually opening tickets one by one or running custom API scripts. There is no simple criteria-based cleanup (filtering by file size, age, extension, or author), and certainly no built-in safeguards to prevent accidental mass deletion.

• Permanent Deletions with No Safety Net: Native attachment deletion in Jira is permanent and immediate. A single misclick can erase audit-critical evidence or production logs with zero native recovery options.

To address these exact gaps without requiring external server infrastructure, we built and recently launched: SBAM — Smart Bulk Attachments (Download, Delete & Trash).

Our client-side architectural approach:

1. 100% Client-Side Streaming (Zero Server Timeouts): Instead of zipping archives on a backend container and racing the 25-second clock, SBAM streams and bundles archives directly inside the browser memory using JSZip in STORE mode. Pre-compressed files (PDFs, images) skip CPU-heavy re-compression, packaging hundreds of files (2+ GB) in just seconds. We also implemented adaptive archive splitting at 400 MB to safeguard browser V8 memory.

2. Targeted Bulk Operations & Storage Cleaner: A streamlined criteria builder that allows admins to filter and bulk-delete attachments across issues by age, file size, extension, or author. To prevent catastrophic mistakes, bulk actions are protected by strict confirmation safeguards. We also included safe in-place file renaming with automatic extension locking to keep project files organized.

3. Smart Anti-Junk Filter (<20 KB): An automated filter detects inline signature icons and tracking pixels below 20 KB, allowing agents to instantly hide them or purge them in bulk.
4. Virtual Trash Vault: A soft-delete retention layer built directly on @Forge/kvs. Files can be safely hidden and restored within a configurable retention window (0 to 9999 days), backed by 3-tier RBAC and automated background cleanup jobs.
5. Strict Zero Data Egress: 100% Forge Cloud-Native. Files and metadata never leave Atlassian’s cloud boundary, ensuring full tenant isolation and compliance.

The app is officially live on the Atlassian Marketplace:
👉 SBAM — Smart Bulk Attachments on Atlassian Marketplace  

Question for Jira & JSM Admins:
How are your teams currently dealing with email signature clutter in Jira Service Management? Do you run custom automation rules to filter them out, or do your agents just suffer through the mess?

I’d love to hear your thoughts on this architecture and what file management headaches give you the biggest trouble day-to-day!

Cheers,
Founder @ Curiosity