Skip to main content

Use File Field in Jira Automation

File Field ships its own automation actions. They're built on Atlassian's Forge automation API, which means they're ordinary rule components: they appear in the rule builder's action picker, run inside Atlassian, and work with any trigger, condition, or branch. There's no webhook to expose, no API token to rotate, and no external service in the path.

Available actions​

ActionWhat it does
Copy attachments to File FieldCopies files from Jira's built-in Attachments into a File Field. Read the guide

More actions are added over time — each gets its own page in this section.

Before you build a rule​

Three things have to be true before an action can do anything useful:

  • The app is installed on the site. The actions come with it; there's nothing separate to enable.
  • A File Field exists and is on the right screens. The action writes the field value directly, so the write doesn't depend on screens — but people only see the result if the field is on the issue view screen for that project and issue type, and the field's context covers them. A rule that appears to do nothing is usually a field that isn't on the screen.
  • You can create the rule. A project-scoped rule needs project admin on that project; a multi-project or global rule needs Jira admin.

Where the actions appear​

In the rule builder, click Add component → Action and search for file field. App-provided actions are listed under Other apps, separately from Jira's built-in ones.

The actions are available in project rules (Project settings → Automation) and in multi-project or global rules (Jira Settings → System → Automation rules) alike.

tip

Just installed the app? Jira caches the list of available actions, so a newly installed action can take a few minutes to appear. If it's not in the picker, wait briefly and reload the rule builder.

How the actions behave when a rule runs​

  • The app connection is explicit. The first time an action is added, the rule builder shows which account it's connected as — for example Connected to File Field for Jira Cloud as …. Use Change connection if the rule should run as someone else.
  • The rule doesn't wait for files to transfer. Actions that move file content hand the work off and let the rule continue, so a large copy never stalls the rest of the rule. The audit log records the action as started, not finished — to confirm a rule works, check the field on a real issue.
  • Limits are checked before anything is written. Each action states its own limits, and a run that exceeds them stops before the first byte moves, leaving the field exactly as it was. See Copy limits for the copy action's numbers.
  • Automated updates are indexed like any other. A field written by a rule is immediately searchable, so filters, boards, and JQL conditions in other rules see it straight away.

Reacting to a File Field, not just writing it​

Actions are half the picture. A File Field is fully searchable, so rules can also branch and gate on what's attached:

  • A JQL condition such as "File Field".FileCount = 0 stops a rule — or blocks a transition — when a required document is missing.
  • FileType and Categories let a rule route work by the kind of document attached.

See Find Issues by Their Files (JQL) for every dimension the field exposes.

What's next?​