Skip to main content
Skip table of contents

Comparison between Jira built-in feature and Attachment Checker

Feature

Jira built-in feature

Attachment Checker

Restrict file extensions

Admins can specify the extensions to allow/block.

(tick)

jira restrict file extensions.png

(tick)

acj restrict file extensions.png

Restrict files without extension

Admins can choose to allow/block files without extension.

(tick)

jira files without extensions.png

(tick)

acj files without extension.png

Restrict related file extensions automatically

Admins only need to specify one extension, all related extensions are implicitly allowed/blocked.

(error)

Admins have to specify all related extensions.
jira related extensions not included.png

(tick)

All related extensions are included automatically.
acj restrict associated extensions.png

Case sensitivity

File extension checks are case-insensitive so admins do not have to specify all combinations.

(error)

Admins have to specify all combinations of uppercase/lowercase for an extension.

(tick)

As an example, exe extension is treated as equivalent to EXE.

MIME type checks

Apache Tika is used to detect the MIME type to prevent bypass of extension check by renaming or removing the file extension.

(error)

Restriction can be easily bypassed by renaming the file extensions.

(tick)

Provides 2 layers of check (File Extension and MIME type).

Exception handling for confidential Microsoft Office files

It is possible to prevent users from uploading confidential files. This MIME type allows the identification of password protected or encrypted Microsoft Office files.

(error)

It is not possible to differentiate an encrypted Microsoft Word (docx) file with the file extension

(tick)

By default, password protected or encrypted Microsoft Office files are not allowed even if the extensions are allowed. This can be granted as an exception.
acj protected and encrypted.png

Backend checks

Checks attachments added via backend:

  • Emails

  • REST APIs

  • ScriptRunner

(error)

Restriction only applies to attachments uploaded via UI.

(tick)

Attachments added via mails will be deleted if file type is not allowed.

Project level settings

Project admins can specify the extensions for different issue types.

(error)

Restriction applies to all projects.

(tick)

Different projects can have different restrictions based on the project purpose/use cases.

Configurable error message

Admins can configure the error message to be displayed when files are blocked.

(error)

Standardized error message.
jira error message.png

(tick)

Allows admins to provide relevant message/instruction to the users.
acj error message.png
acj configurable error message.png

Support 3rd party apps

Checks attachments added via 3rd party apps' endpoints:

(error)

Checks are only done for Jira’s attachments.

(tick)

Support checks for 3rd party apps which uploads/stores the attachments differently. Admins can also choose to include or exclude these apps from the file type check.
acj file type check exclusions.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.