Jira & JSM App
File Field
A dedicated attachment field for Jira & JSM.
Jira's built-in attachments are one unstructured pile with no rules. File Field adds a native attachment custom field — set the allowed file types, count, and size, make it required, and keep every file inside Atlassian.
RUNS ON ATLASSIANFREE UP TO 10 USERS30-DAY FREE TRIAL
What's missing from Jira's built-in attachments
When a specific document matters — a signed contract, a screenshot, a compliance record — Jira gives you no dedicated place for it and no rules to enforce.
One unstructured pile
Jira's built-in attachments dump everything into a single list. There's no dedicated place for the signed contract, the ID scan, or the compliance record.
No upload rules
Anyone can attach any type, any size. Nothing stops a 2 GB video where you expected a one-page PDF — or the wrong file entirely.
Can't be required
The built-in attachment field cannot be made mandatory, so issues slip through without the document they were supposed to carry.
No control on the portal
On the JSM customer portal there are no rules either, leaving agents to sort through whatever files happen to land on a request.
See File Field in action
From a dedicated field to colored categories — every part designed to bring order to your attachments.
A dedicated attachment field
File Field is a native Jira custom field. An admin adds it like any other field and it renders directly in the issue view, the create-issue form, and workflow transitions — no separate panel or pop-up to load.
Feature:
Attach multiple files per field. Each appears as a card with its name, type, and size, plus Download and Delete actions. The field saves automatically — there is no separate Save button.
Benefit:
Every important document gets its own named home instead of disappearing into one shared pile of attachments.
Set the rules: types, count, and size
Each field context has its own upload policy. Choose the allowed file types from the built-in catalog — PDF, images, Word, Excel, CSV, ZIP and more — or leave it open to any type. Set how many files the field can hold and how large each one may be.
Feature:
Per-context rules for allowed file types, maximum file count (default 1), and maximum file size (default 100 MB). Everything is checked before anything uploads, with all problems shown at once.
Benefit:
Different projects get different policies from the same field, and files that break the rules never make it in.
Make attachments required
Because File Field is a native Jira field, you can make it mandatory through Jira's own field configuration. Jira then enforces that at least one file is attached before an issue can be created, edited, or transitioned.
Feature:
Toggle Required in Jira's field configuration. The asterisk and validation are Jira's own, and they apply only to the projects and issue types that context covers — not your whole instance.
Benefit:
Issues can't move forward without the document they need — no more chasing a missing contract after the fact.
Classify files with colored categories
Tag each file with a colored label — Contract, ID Document, Certificate. One field can then hold a varying mix of documents, even several of the same kind, while keeping each one easy to tell apart at a glance.
Feature:
Optional per-context categories in six colors. Pick one when attaching a file, or leave it as none. Labels show on every file, travel with Jira exports, and are searchable through the field's Categories JQL alias.
Benefit:
One labeled field absorbs a whole variable pile of documents and keeps every one organized, exportable, and findable.
Collect files on the JSM portal
File Field works on the Jira Service Management customer portal, so customers can attach files when they raise or update a request — no Jira access required. Agents see those files on the same field in the issue view.
Feature:
Add it to a request type's form like any custom field — no portal-specific setup. The same allowed types, file count, and size rules apply to customers, and files are stored inside Atlassian.
Benefit:
Service teams collect the right files from customers up front, instead of asking for them in a string of follow-up comments.
More features
Expand for the details — validation, automatic save, JQL search, exports, and permission-aware access.
- Validation before upload — the whole selection is checked and every problem shown at once
- JQL search — find issues by file category through the field’s Categories alias
- Included in exports — file names and categories travel with your Jira exports
- Permission-aware — every upload, download, and delete follows Jira permissions
- Up to ~1 GB per file — a generous ceiling, with the 100 MB default safely below it
Business benefits for Jira teams
File Field turns a free-for-all of attachments into structured, dedicated fields your team and your auditors can trust.
Replace one unstructured pile with named fields and enforced rules. Everyone knows where each document belongs and exactly what is allowed in it.
Files never leave Atlassian and access mirrors your Jira permissions, so there is no extra vendor and no parallel permission model to audit.
No third-party bucket, API key, or login to secure. Files live in the same Atlassian cloud as your issues, covered by the boundary you already assessed.
Built for teams that handle important files
Real scenarios from HR, legal, and service teams — and how File Field handles each one.
HR & Onboarding
- Collect a contract, an ID scan, and however many certificates a hire has — all in one labeled field
- Make the contract field required so no one is onboarded without it
- Restrict to PDF and images, capped at a sensible size
- Find issues missing a document with a JQL category search
Legal & Compliance
- Keep a contract with its amendments and consent forms together, each categorized
- Mark files holding personal data so they are easy to find and remove for GDPR
- Keep everything inside Atlassian — no external processor to add to audits
- Export file names and categories for external records
IT & Service Management
- Let customers attach screenshots, logs, and recordings on the JSM portal
- Enforce allowed types and a size cap so requests arrive complete
- Agents see and manage the same files on the issue view
- Categorize attachments so automation can act on what a file is
Up and running in under 5 minutes
Install from Marketplace
Add File Field to your Jira Cloud site. No configuration is needed during installation.
Add the field & set rules
Create the field, place it on your screens, and set the allowed types, file count, and size.
Attach your first file
Open an issue, drop a file into the field, and it is attached right away — ready to download or remove.
Built for secure Jira Cloud operations
Files are stored within Atlassian infrastructure and access follows your Jira permissions. No external servers, no third-party data transfer.
File Field – Attachment Custom FieldJira & JSM app by Terano Apps
Jira CloudCustom FieldForge
Jira & JSM app with a free tier up to 10 users and a 30-day trial for larger teams.
Built on Atlassian Forge
Runs natively inside Jira Cloud with Atlassian's security, sandboxing, and hosting infrastructure.
Files stay inside Atlassian
Every file is stored on Atlassian's own infrastructure, alongside your Jira data. Nothing is sent to an external service.
Permission-aware access
Every upload, download, and delete is checked against the user's Jira permissions for the issue.
Give every file a home in Jira
Start a free trial — no credit card, no commitment. Free for up to 10 users, with full support during the trial.
Start free trial on Marketplace