Skip to main content

FAQ

Where are the uploaded files stored?

Inside Atlassian. Files are stored on Atlassian's own infrastructure, alongside your other Jira data, and are never sent to any external or third-party service. See Data & Security for the full picture.

How many files can I attach to one field?

By default, up to 20 files per field. An administrator can change this limit for each field context in the upload rules. The count is cumulative — files already attached plus the ones you're adding must stay within the limit.

Is there a maximum file size?

By default, 100 MB per file. An administrator can change this for each field context, choosing the unit (B, KB, MB, or GB) in the upload rules.

There is also a platform ceiling of just under 1 GB per file. A file larger than that can't be uploaded regardless of the configured limit, and setting the limit above ~1 GB won't raise the real ceiling — the 100 MB default sits comfortably below it. Empty (0-byte) files are not accepted.

Which file types are allowed?

Whatever an administrator chooses for that field context. The built-in catalog covers PDF, PNG, JPEG, GIF, WebP, plain text, CSV, Word (.docx), Excel (.xlsx), and ZIP, and a custom type can be added as well. If no types are selected, all file types are allowed. See Set Field Configuration.

Who can download or delete a file?

Access always follows your Jira permissions. Downloading a file requires permission to browse the issue it belongs to; deleting one requires Edit Issue permission on that issue. A file can only be reached through the issue it's attached to — there's no cross-issue access. See Data & Security for the full breakdown.

Can I make the field mandatory?

Yes — through Jira's field configuration, exactly like any other field. Jira then enforces it: the user must attach at least one file before the issue can be created, edited, or transitioned. This is separate from the upload rules. See Make the Field Required.

What happens if a file breaks the rules?

The file is checked before it's uploaded. If something is wrong — an unsupported type, a file that's too large, or too many files for the field — the whole selection is rejected and you're shown all the problems at once, so you can fix everything before trying again. Nothing is uploaded until the selection passes.

Do I need to save after attaching or removing a file?

No. The field saves automatically after a successful upload or delete — there's no separate Save button in the field editor.

Does File Field work on the Jira Service Management portal?

Yes. Customers can attach files to a request directly from the JSM customer portal, and agents see those files on the field in the issue view. See Use on the JSM Portal.

Can I find or export which issues have files?

Yes. The field's value — the list of file names, or None when empty — appears in issue views and is included when you export. You can also search with JQL using the field's aliases: ComplianceState = configured finds issues that have files, and ComplianceState = missing finds those that don't.

I selected two files of the exact same size and their names look swapped. Why?

When two files selected together have an identical byte size, the app can occasionally assign their names ambiguously. Both files always keep a real filename — never a placeholder — but with two identical sizes the pairing of name to file can be uncertain. If this matters, attach those files one at a time.

What's next?​