Skip to main content

Make the Field Required

Because File Field is a native Jira field, you can make it mandatory the same way you would any other field — through Jira's field configuration.

It helps to keep two settings separate:

  • Upload rules (the field's configuration) decide what may be attached — allowed types, file count, and file size. See Set Field Configuration.
  • Required (Jira's field configuration) decides whether a file must be present at all. That's what this page covers.

Mark the field as required

  1. Go to Jira Settings (cog icon, top right) → Work items → Field configurations.
  2. Open the field configuration used by the relevant projects and issue types.
  3. Find your File Field in the list and choose Required.
Default Field Configuration in Jira admin — the Signed Contract field with the Required toggle enabled

Enable the Required toggle for the field in Jira's field configuration

That's all File Field needs — Jira itself handles the enforcement from here, so there's nothing to configure in the app for this.


What users see

With the field set to required, Jira enforces that at least one file is attached before the issue can be saved. If someone tries to create, edit, or transition an issue with the field empty, Jira blocks the action and flags the field as required — exactly as it does for any other mandatory field. Once a file is attached, the issue saves normally.

Create-issue form — the Signed Contract field marked with an asterisk and a "Signed Contract is required" validation error

Jira flags the field and blocks saving until at least one file is attached


What's next?