SBAM — Smart Bulk Attachments (Download, Delete & Trash)

Pretty useless except to hide the duplicate/junk files in a single JIRA ticekt view screen. In the Smart Attachments section I cannot even view a thumbnail of what is inside the attachment files and have to download them to know what they are. Finally the Smart Attachments app seems not to be able to work even when I have selected only 5 JIRA tickets. It comes up with an error: Error: Failed to communicate with Jira Search API: There was an error invoking the function - Response payload size exceeded maximum allowed payload size (6291556 bytes).

• 

  Curiosity

  Hi James,

  Thank you for taking the time to share your feedback. Thanks to it I shipped an immediate production fix.

  1. Resolution of the 6 MB Payload Error

  Short Answer: The 6 MB payload crash has been completely resolved in my latest release.

  Long Answer: The error "Response payload size exceeded maximum allowed payload size (6291556 bytes)" occurred because Atlassian Forge enforces a strict 6 MB limit on synchronous response payloads. I implemented a 3-step architecture to fix this:

  - Strict Budget Guard: The backend now enforces an internal budget ceiling (<5 MB), ensuring responses never exceed Forge limits regardless of how many thousands of files exist on the tenant.

  - Payload Optimization: I stripped redundant metadata fields from the search response, reducing payload weight by over 50%.

  - Resilient Fallback: Implemented an automated query fallback to guarantee views always render cleanly without breaking.

  2. Why Selecting 5 Tickets Triggered This Behavior

  Short Answer: Due to Atlassian platform constraint in Jira's new "All work" list view, Jira does not pass row-level checkbox selections to the top-level "Apps" menu, causing the app to query your entire instance instead.

  Long Answer: When you selected 5 tickets, Jira passed an empty selection array (issueKeys: []) to my app. Instead of the specific tickets, Jira sent the broad search filter of the entire view (e.g., created >= -30d). Consequently, the app was directed to query the broader issue set across the instance, triggering the payload limit on instances with heavy attachment density. My query resolver now handles this gracefully. You can also target specific tickets at any time by entering keys or JQL (e.g., issueKey in (KEY-1, KEY-2)) directly in SBAM's search bar.

  3. File Thumbnails & Quick Preview

  Short Answer: I completely agree with you. An in-app Quick Preview engine is already built and will be available in an upcoming release.

  Long Answer: Having to download multiple files just to check their contents creates unnecessary friction. I have completed development of an in-app Quick Preview engine (supporting inline previews for images, PDFs, and text/logs directly within Jira without requiring local downloads). It is currently in active staging testing and will be rolled out shortly.

  If the latest update resolves these friction points for your team, I would be grateful if you'd consider updating your review.

  Best regards,

  Patryk (Developer of SBAM)