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, 1 file per field — a single file. 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.

Do I have to download a file to see what's in it?

No. Images, PDF documents, CSV tables, and text files can be opened straight from the field — click the field, then the eye icon on the file. A PDF scrolls through all its pages, a CSV opens as a table, text can be searched, and the arrow keys step to the next file. It works on the issue view and on a create screen, a transition screen, or a JSM portal request before the form is saved. The preview follows the same permissions as a download, and nothing is copied to your computer. See Preview Files Without Downloading.

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 an attachment field required in Jira?

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.

I made the field required, but an issue was created without a file. Why?

Until the release of 20 August 2026, attaching a file and then removing it before submitting left the field counting as filled, so the form went through with nothing attached. A field nobody had touched was always caught correctly — it was only the attach-then-remove case that got past the check. Current versions block it on the create-issue form, transition screens, and the JSM portal alike.

To find the issues that slipped through earlier, search for the value they still carry:

"File Field".FileCount = 0

Open the field for editing on such an issue and save it to clear the leftover value. See Find Issues by Their Files (JQL).

Does making it required affect the whole Jira instance?

No. Because File Field is a separate custom field, marking it required applies only to the field configuration that covers the relevant projects and issue types — not to Jira's built-in Attachment field or to your whole instance. 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 label or classify the files in a field?

Yes. An administrator can turn on categories for a field context and define a set of colored labels (for example Contract, ID Document, Certificate). When categories are on, you pick one before a file uploads — or leave it as none. The label shows above the file, is included in exports, and is searchable in JQL. See Classify Files with Categories.

Can I give everyone a template or a procedure to download from the field?

Yes. An administrator can publish reference documents on a field context — up to ten files, up to 30 MB each, in any type. They appear in their own section above the field's files, wherever the field renders: the issue, the create-issue form, a transition screen, and the JSM portal. Everyone who uses the field can download them and open them in the preview. See Publish Reference Documents.

Do reference documents count toward the field's file limit?

No. They are part of the field's configuration, not its value. They don't count toward the maximum number of files, don't appear in Jira exports or in JQL searches, and don't satisfy a required field — someone still has to attach a file of their own.

Can a user delete or replace a reference document?

No. Reference documents are read-only for everyone except an administrator, who manages them in the Documents tab of the field configuration. There is no version history: replacing a document means removing the old one and adding the new one.

Are reference documents copied when Automation copies a File Field?

There is nothing to copy. The Copy File Field action copies the field's value — the files someone attached. Reference documents belong to the field context, so they already appear on the destination work item if that context covers it.

Can I see 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 filter issues by their files directly in JQL — by presence (is EMPTY), count, type, name, or category. See Find Issues by Their Files (JQL).

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?​