Skip to main content
Jira & JSM App
File Field app logo

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
0Max file size per file
0Validated before every upload
0Files stay in Atlassian

What's missing from Jira's built-in attachments

When a specific document matters, 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.

A dedicated attachment field

A native Jira custom field an admin adds like any other — it renders in the issue view, the create form, and workflow transitions. Attach multiple files per field, each with Download and Delete, and give every important document its own named home instead of one shared pile.

Set the rules: types, count, and size

Each field context gets its own upload policy, so different projects can have different rules: allowed file types from a built-in catalog (PDF, images, Word, Excel, CSV, ZIP and more), a maximum file count, and a maximum size. Everything is checked before anything uploads, so 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 in Jira's own field configuration. Jira then enforces at least one file before an issue is created, edited, or transitioned — and only in the projects and issue types that context covers, not your whole instance.

Classify files with colored categories

Tag each file with a colored label — Contract, ID Document, Certificate — in six colors you define per context. One field then holds a varying mix of documents, even several of the same kind, and the labels travel with your Jira exports and are searchable through the field's Categories JQL alias.

Collect files on the JSM portal

File Field works on the Jira Service Management customer portal, so customers attach files when they raise or update a request — no Jira access needed, no portal-specific setup. The same allowed types, count, and size rules apply to them, and agents see those files on the same field in the issue view.

Preview without downloading

Open images, whole PDFs, CSVs as tables, and searchable text files straight from the field — no download, no second application.

Reference documents

Publish a template or a procedure on the field itself, read-only, so people fill it in correctly the first time.

Files up to ~1 GB

A generous ceiling per file, with the 100 MB default sitting safely below it.

Built for teams that handle important files

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
  • Publish the blank contract and the onboarding checklist on the field that collects them back

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
  • Show customers the request template on the portal before they submit anything

Up and running in under 5 minutes

01

Install from Marketplace

Add File Field to your Jira Cloud site. No configuration is needed during installation.

02

Add the field & set rules

Create the field, place it on your screens, and set the allowed types, file count, and size.

03

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 stay on Atlassian infrastructure and access follows your Jira permissions.

File Field logo
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