Skip to main content

Jira Attachment Management Apps Compared: Bulk Downloader vs Attachment Reviewer

· 11 min read
NGPilot
NGPilot
NGPilot

Jira issues accumulate attachments fast -- screenshots from QA, log files from production incidents, design mockups from product, contracts from legal. Before long, a single project can hold thousands of files across hundreds of issues. Two questions come up repeatedly: "How do I download all of these at once?" and "How do I make sure the right files -- and only the right files -- are attached?"

NGPILOT builds two apps that address these questions from different angles. Simple Bulk Attachment Downloader for Jira handles bulk exports -- downloading many attachments in one organized ZIP. Attachment Reviewer for Jira handles inbound control -- enforcing file type and size policies on every upload. This post compares both in detail so you can decide which one your team needs (or whether you need both).

The Attachment Management Problem in Jira​

Out of the box, Jira gives you basic attachment functionality. You can upload files to issues, view them, and download them one at a time. For small teams with a handful of issues, that works. But as projects scale, the gaps become painful:

  • No bulk operations. Need to download every attachment from 50 bug reports for an audit? You are clicking through 50 issues and downloading files one by one. There is no native "export all attachments" button.
  • No upload guardrails. Someone uploads a 200 MB video to a support ticket. Someone else attaches an .exe file to a production bug. Jira accepts everything by default. There is no built-in way to say "only allow PDFs and images in this project."
  • No organization on export. When you eventually download attachments for archiving or sharing, they land in your Downloads folder as a flat list. No folder structure, no connection to the issues they came from.
  • Storage costs creep up. Jira Cloud storage limits are tied to your plan. Unchecked large attachments eat into your quota, and there is no native mechanism to enforce size policies per project.

These problems split into two categories: outbound (getting attachments out of Jira efficiently) and inbound (controlling what attachments go into Jira). That is exactly why we built two separate apps rather than one combined tool. Each does one job well.

Simple Bulk Attachment Downloader for Jira​

Simple Bulk Attachment Downloader for Jira is the outbound solution. It lives in the Jira issue navigator and lets you download all attachments from any set of search results as a single ZIP file.

How It Works​

  1. Run any search. Use JQL, saved filters, or quick search to find the issues you care about.
  2. Click the app button. A "Simple Bulk Attachments Downloader" button appears in the issue navigator toolbar.
  3. Review the summary. The app shows how many issues were found, how many attachments will be downloaded, and the estimated total size.
  4. Download. Click the download button and the app fetches all attachments in parallel, packages them into a ZIP, and sends it to your browser.

No configuration required. The app works immediately after installation.

Key Features​

Parallel downloading. The app uses concurrent downloads to fetch attachments 3-8x faster than downloading them one at a time. It automatically adjusts concurrency based on the number of files.

Organized ZIP structure. Files are not dumped into a flat archive. Each issue gets its own folder named with the issue key and summary (for example, PROJ-123 - Login page crash/screenshots). Original filenames are preserved, and duplicate names are handled without overwriting.

JQL integration. Any JQL query or saved filter works. Search by project, label, date range, fix version, assignee, or any other criteria. The app downloads attachments from exactly the issues your search returns.

Permission-aware. The app only downloads attachments from issues you can access. If your Jira permissions restrict you to certain projects or issue types, those restrictions are respected. No data leaks through the download process.

Real-time progress. As files download, you see live progress tracking. If any individual file fails, the app creates an error entry in the ZIP so you know what went wrong rather than silently skipping it.

Browser-native delivery. The ZIP downloads through your browser's built-in download manager. No external storage, no cloud intermediary. Files go directly from Jira to your machine.

Common Use Cases​

  • QA teams downloading test evidence (screenshots, logs, video captures) from all test execution issues for compliance reporting
  • Project managers collecting deliverables and documents from all issues in a release or sprint for stakeholder review
  • Support teams archiving customer-provided files from resolved tickets before closing a milestone
  • Development teams packaging release artifacts, specs, and design assets tied to a specific version
  • Auditors exporting all attachments from issues flagged during a compliance review

Learn more in the Simple Bulk Attachment Downloader documentation.

Attachment Reviewer for Jira​

Attachment Reviewer for Jira is the inbound solution. It validates every file uploaded to your Jira issues against configurable policies and automatically removes non-compliant attachments.

How It Works​

  1. A user uploads a file to any Jira issue through the web interface, mobile app, or API.
  2. The app validates automatically. Attachment Reviewer checks the file against the project's rules -- file type and file size.
  3. The file passes, warns, or fails. Passed files stay. Failed files are removed immediately. Warned files stay but generate a notification.
  4. A comment is posted. The issue gets a validation report comment explaining what happened.

Everything happens in milliseconds. The user sees the result as a comment on the issue, usually before they navigate away.

Key Features​

File type policies. Two modes are available. Whitelist mode (recommended) allows only explicitly approved file extensions -- for example, pdf, docx, png, xlsx. Everything else is blocked. Blacklist mode allows all file types except those explicitly blocked. Whitelist is more secure; blacklist is more flexible.

Comprehensive default blocklist. The app ships with a curated blocklist covering executables (exe, msi, bat, cmd), scripts (vbs, ps1, sh, bash), system files (sys, dll, drv), Java archives (jar, war, ear), mobile packages (apk, ipa, dmg), macro-enabled documents (docm, xlsm, pptm), and more. Blocked types always take precedence, even in blacklist mode.

File size enforcement. Set a maximum file size (1 MB to 500 MB, default 25 MB) that hard-blocks oversized uploads. Set a separate warning threshold (default 10 MB) that allows the file but alerts the team. This two-tier system lets you discourage large attachments without breaking workflows that genuinely need them.

Project-level configuration. Each Jira project has independent settings. Development projects can allow code files (js, py, java). Design projects can set higher size limits for images. Documentation projects can restrict to PDFs and office documents. General projects use the secure defaults.

Automatic removal and feedback. When a file fails validation, it is deleted from the issue automatically. No manual cleanup needed. A validation report comment is posted with the file name, type, size, and the specific rule that was violated. Users know exactly what went wrong and how to fix it.

Zero content inspection. The app only checks metadata -- file extension, MIME type, and file size. It does not read file contents. No data leaves Atlassian's infrastructure. The app runs on Atlassian Forge, which means it stays within Atlassian's secure cloud platform.

Common Use Cases​

  • Security-conscious organizations blocking executables, scripts, and macro-enabled documents from being uploaded to any issue
  • Storage management enforcing file size limits per project to keep Jira storage usage under control
  • Compliance teams requiring that only approved file types are attached to audit-related issues
  • Multi-project organizations applying different rules per project -- strict for production issues, relaxed for internal tooling
  • External collaboration projects where outside users submit files and you need to enforce what file types are accepted

Learn more in the Attachment Reviewer for Jira documentation.

Feature Comparison​

FeatureSimple Bulk Attachment DownloaderAttachment Reviewer
Primary purposeBulk export attachments from JiraEnforce file policies on uploads
DirectionOutbound (Jira to local machine)Inbound (local machine to Jira)
TriggerManual -- click from issue navigatorAutomatic -- runs on every upload
JQL integrationYes -- download from any search resultsNot applicable
File type filteringNo -- downloads all attachmentsYes -- whitelist or blacklist modes
File size limitsNo -- downloads all sizesYes -- max size and warning threshold
Parallel processingYes -- 3-8x faster concurrent downloadsNot applicable (single-file validation)
ZIP packagingYes -- organized by issue foldersNo
Permission awarenessYes -- respects Jira read permissionsYes -- requires project admin for settings
Per-project configurationNo -- works globallyYes -- independent settings per project
Automatic enforcementNo -- user-initiated actionYes -- validates every upload automatically
Comment feedbackNoYes -- validation report on every upload
Configuration requiredNone -- works after installMinimal -- secure defaults work immediately
PlatformJira Cloud (Atlassian Forge)Jira Cloud (Atlassian Forge)
PricingSee Atlassian MarketplaceSee Atlassian Marketplace

When to Use Each App​

The two apps solve different problems. Here are the scenarios where each one -- or both -- is the right choice.

Use Simple Bulk Attachment Downloader When...​

You need to archive project attachments. A project is wrapping up and you need to download every file for long-term storage outside Jira. Run a search for all issues in the project, click download, and you have a complete, organized archive.

You are preparing for an audit. Auditors want all supporting documents from issues tagged with a specific label. Search by label, download the ZIP, and share it with the audit team. The folder structure ties every file back to its issue.

You are migrating or backing up. Before a major configuration change, project split, or data migration, you want a local copy of all attachments. One download gives you everything organized by issue.

Your team reviews deliverables in bulk. A QA manager needs all test evidence from the last sprint. A product manager wants all design mockups from stories in the current release. Search, download, review locally.

Use Attachment Reviewer When...​

Security is a priority. You do not want .exe files, shell scripts, or macro-enabled documents anywhere in your Jira instance. Set whitelist mode and only approved file types get through. The default blocklist handles the most common threats out of the box.

Storage costs are a concern. Your Jira Cloud plan has storage limits and large attachments are consuming your quota. Set file size limits per project to prevent users from uploading files that do not belong in Jira.

You have external collaborators. Customers, vendors, or contractors submit files through Jira Service Management or shared projects. Attachment Reviewer ensures only the file types you approve are accepted, regardless of who uploads them.

Compliance requires documented policies. Your organization needs proof that file upload policies are enforced. Every validation creates an audit trail in the issue comments, showing what was allowed, warned, or blocked and why.

Different projects need different rules. Your development projects need to allow code files. Your HR projects should only accept PDFs and images. Attachment Reviewer lets you configure rules independently per project.

Use Both When...​

Many teams benefit from using both apps together. Attachment Reviewer keeps your Jira instance clean and secure by controlling what goes in. Simple Bulk Attachment Downloader gives you an efficient way to get everything out when you need it.

A practical combined workflow:

  1. Attachment Reviewer runs on every upload, ensuring only compliant files enter your Jira projects.
  2. Over time, issues accumulate clean, policy-compliant attachments.
  3. When you need to export -- for audits, archiving, migration, or sharing -- Simple Bulk Attachment Downloader pulls everything out in one organized ZIP.

The result: your Jira instance stays clean, and exporting is always one click away.