Skip to main content

Changelog

This page lists notable changes shipped with each release of File Field. The most recent update is shown first.

info

The app is updated through the Atlassian Marketplace. Your Jira Cloud site receives new versions automatically — no manual upgrade is required.

Release: 2026-08-20​

Required fields catch a removed file​

A File Field marked required now blocks the form when its last file has been removed. Previously, attaching a file and then deleting it before submitting left the field counting as filled, so the issue saved with nothing attached.

  • Fixed on every screen where the field is filled — the create-issue form, transition screens, and the Jira Service Management portal. A field nobody touched was always caught; it's the attach-then-remove case that got through.
  • An empty field is now genuinely empty — in Advanced search, "File Field" is EMPTY finds issues with no files. FileCount = 0 no longer matches a field whose files were removed. Issues emptied before this release keep the old value, so "File Field" is EMPTY OR "File Field".FileCount = 0 matches both.

See Make the Field Required and Find Issues by Their Files (JQL) for the full guide.

Release: 2026-08-16​

Reference documents​

An administrator can now publish files on a File Field — a template to fill in, a procedure to follow, a worked example — so everyone who uses that field can read them.

  • Published once per field context — up to ten documents, up to 30 MB each, in any file type, set in the new Documents tab of the field configuration.
  • Your own heading and instruction — name the section and tell people what to do with what's in it.
  • Everywhere the field appears — the issue, the create-issue form, transition screens, and the Jira Service Management portal.
  • Read-only, and never the field's value — documents can be downloaded and previewed but not changed, and stay out of exports and JQL.

See Publish Reference Documents and Read Reference Documents for the full guide.

Release: 2026-08-15​

Preview files from the issue view​

A file can now be opened for reading straight from the issue, without putting the field into edit mode first.

  • An eye icon next to Download — on the file card and on every file in the list.
  • The same preview as in the editor — images, PDFs, CSV as a table, searchable text, and arrows for stepping between the field's files.
  • A tidier file list — one file per line, with its actions beside the name.
  • Minor updates and bug fixes.

See Preview Files Without Downloading for the full guide.

Release: 2026-08-14​

A fuller file preview​

The preview now behaves like the app you'd otherwise open the file in — whole PDFs scroll, spreadsheets open as tables, text is searchable, and you can step between a field's files without closing the dialog.

  • Whole PDFs, not one page at a time — every page in one continuous scroll, fitted to the width of the dialog, with zoom buttons and a page counter. Long documents stay responsive: only the pages near you are drawn.
  • CSV and TSV as a table — columns line up and the header row stays in view while you scroll, with one button to switch to the raw text. A file that isn't really a table simply opens as text, as before.
  • Find in a text file — a search box with a match count and next/previous, color for source and configuration files, line numbers you can hide, and a text size you can step up or down.
  • Step between files — arrows at the sides of the preview, and the ← and → keys, move through the field's files, so several documents can be checked without closing and reopening.
  • Preview before the form is saved — files attached on the create screen, a transition screen, or a JSM portal request can be opened straight away, instead of only after the form is submitted.
  • Nothing new to grant — the preview still follows the same permissions as a download, and needs no extra configuration or app permissions.

See Preview Files Without Downloading for the full guide.

Release: 2026-08-13​

Preview files without downloading​

A file attached to a File Field can now be opened and read on the issue, so checking what's in a document no longer means downloading it first.

  • Images, PDFs, and text files — including logs, CSV exports, JSON, and configuration files. The eye icon appears on the files the preview can open; anything else downloads as usual.
  • Tools where you need them — one row of icons above the file, carrying the actions that make sense for what you're looking at, with Download always among them.
  • Files up to 150 MB — anything over 25 MB states its size and asks before it starts, then shows progress you can cancel.
  • Nothing to configure, nothing to grant — the preview follows the same permissions as a download and works as soon as the app is installed.

See Preview Files Without Downloading for the full guide.

Release: 2026-07-30​

Copy files from one issue to another​

A File Field can now be filled from another issue's File Field, so files gathered on a request travel to the work item created from it — without carrying across everything else that was attached.

  • New action — Copy File Field to another work item — copies the files held in one File Field onto a File Field on a different issue, as a step in an automation rule.
  • Four inputs — the issue and File Field the files are read from, and the issue and File Field they're copied to. They're separate because a File Field's context is set per project and issue type, so the two are often genuinely different fields.
  • Smart values on both issues — point the target at {{createdIssue.key}} to fill the issue a rule has just created.
  • The source keeps its files, the target's are replaced — the original field is untouched; whatever the receiving field held before is removed.
  • The same copy limits — up to 50 files, 100 MB per file, and 500 MB per run, all checked before anything is copied.

See Copy File Field to Another Work Item for the full guide.

Release: 2026-07-26​

Fill a File Field from Jira Automation​

File Field now adds its own action to Jira Automation, so a rule can put files into the field without anyone uploading them by hand.

  • New action — Copy attachments into File Field — copies files from Jira's built-in Attachments into a File Field as a step in an automation rule.
  • Choose the source and the target — set which issue the attachments are read from, using a smart value such as {{issue.key}} or a literal issue key, and pick the receiving File Field by name from a dropdown.
  • Files keep their details — name, type, and size are preserved, and the copies behave exactly like files attached by hand, including download and JQL search.
  • Originals stay where they are — the action copies, it never moves or deletes anything from Attachments.
  • Clear copy limits — up to 50 files, 100 MB per file, and 500 MB per run, all checked before anything is copied, so a run either completes or leaves the field untouched.

See Copy Attachments into File Field for the full guide.

Release: 2026-07-03​

Search files in JQL​

File Field is now fully searchable in Advanced search (JQL), so you can filter issues by what's attached and reuse those queries in saved filters, boards, and automation.

  • Search by file count — find issues that are missing a required document (FileCount = 0) or that carry several, with the field's FileCount alias.
  • Search by file type — filter by broad families such as PDF, Image, Word, or Spreadsheet using FileType.
  • Search by file name — match issues by the words in a file's name with FileName.
  • Search by category — filter by the category a file was given through Categories.
  • Works in automation — the same conditions run in automation rules, for example blocking a move to Done when no file is attached.

See Find Issues by Their Files (JQL) for the full guide.

Release: 2026-07-02​

A refreshed file editor​

We've rebuilt the field's edit experience to make attaching and organizing files clearer and more reliable.

  • File cards with type icons — each file now shows an icon for its kind (image, audio, video, document, and more), so you can tell files apart at a glance in both the editor and the issue view.
  • Simpler category picking — choose a category with one click on a colored label, right next to the file, instead of a dropdown.
  • Cleaner file list — files in the issue view show their name, type, and size, with a download button on each.
  • Safer editing — Save now waits until any in-progress upload finishes, and cancelling an edit no longer leaves the field pointing at a removed file. Files you just uploaded download correctly straight away.

Release: 2026-06-28​

File categories​

Label each file with a colored category, so a single field can hold different document types and keep them easy to tell apart.

  • Per-context categories — enable and define categories independently for each field context. Off by default, so existing fields are unchanged.
  • Six label colors — name a category and pick from Grey, Blue, Green, Red, Purple, or Yellow, with a live preview.
  • Choose on upload — when categories are on, people pick a category before files upload, or leave it as none.
  • Visible everywhere — the colored label shows above the file in the issue view and editor, and is included in Jira exports.
  • JQL search — find issues by category using the field's Categories alias.

See Classify Files with Categories for the full guide.

Release: 2026-06-25​

Initial release​

File Field is a native Jira custom field for attaching multiple files directly to issues and Jira Service Management portal requests.

  • Multiple files per field — attach as many files as the policy allows, all in one named field.
  • Per-context upload rules — administrators set the allowed file types, maximum number of files, and maximum file size independently for each field context.
  • Files stay inside Atlassian — built on Atlassian Forge; nothing is sent to external or third-party services.
  • Permission-aware — every upload, download, and delete is checked against the user's Jira permissions.
  • JSM portal support — customers can attach files when raising or updating a request from the customer portal.
  • Required field support — the field works with Jira's standard field configuration, so it can be made mandatory on any issue type.
  • Works everywhere — issue view, create-issue form, workflow transition screens, and the JSM customer portal.