Supported Field Types
Formify works on Jira's system fields and on the standard custom field types. Use this page to check, before you plan a rule, that the field takes that kind of rule on that screen.
Every field in the tables takes Visibility, Required, Read-only, Name and Description rules unless its row says otherwise. The columns show what differs from field to field: whether a rule can set the field's value, limit its options, and read it in a Field value condition. The work item view has no Required, Value or Validation rules for any field (see Defining Actions).
Where the rule editor offers more than this page lists, the page is what Jira applies: such a rule saves, but has no effect.
Check a system field
| Field | Value | Options | In conditions | Screens and rules that differ |
|---|---|---|---|---|
| Summary | Yes | No | Yes | No Required rule: Jira always requires it. On the work item view, Read-only only. |
| Description | Yes | No | Yes | On the work item view, no Description rule. |
| Issue type | Yes | Yes | Yes | Value and Options rules only, in the Create dialog and transition dialogs. |
| Priority | Yes | Yes | Yes | On the work item view, no Description rule. |
| Assignee | Yes, also smart values | No | Yes | |
| Reporter | Yes, also smart values | No | Yes | |
| Labels | Yes, also smart values | No | Yes | |
| Due date | Yes, also smart values | No | No | Create dialog only. |
| Components | No | No | No | Create dialog and work item view. |
| Fix versions | No | In transition dialogs | No | |
| Affects versions | No | No | No | |
| Parent | No | No | No | |
| Original estimate | No | No | No | Work item view and transition dialogs. |
| Resolution | No | No | No | Transition dialogs only. No Required rule. |
| Status | No | No | Its own condition | No rules. The Issue status condition reads it on the work item view and in transition dialogs. |
Check a custom field type
| Field type | Value | Options | In conditions | Screens that differ |
|---|---|---|---|---|
| Text field (single line) | Yes | No | Yes | |
| Paragraph | No | No | No | |
| URL | Yes | No | Yes | |
| Number | Yes | No | Yes | |
| Select list | No | Yes | Yes | |
| Radio buttons | No | Yes | Yes | |
| Multi-select list | Yes | Yes | Yes | |
| Checkboxes | Yes | Yes | Yes | |
| Cascading select | Yes | No | No | |
| Date picker | Yes, also smart values | No | No | |
| Date time picker | Yes, also smart values | No | No | |
| User picker | Yes, also smart values | No | No | |
| Multi-user picker | Yes, also smart values | No | No | |
| People | No | No | No | Create dialog and work item view. |
| Project picker | No | No | No | |
| Target start, Target end | No | No | No | Create dialog only. |
A Story Points field of the Number type works like any number field: in conditions, with Set value and with the number validations.
On a cascading select, Set value takes the parent option and, if needed, a child option.
Check what a condition or a validation can do with the field
A "Yes" under In conditions means a Field value condition can read the field. The operators depend on the field type: see Operators by field type. On the work item view and in transition dialogs, a condition can also read a select list, radio buttons, multi-select list or checkboxes field that isn't on the screen, from the value saved on the work item.
Validations go by the kind of value: presence checks work on any field, date checks on date fields, number checks on number fields and text checks on text fields. The full table is in Defining Field Validations.
Smart values are described in Using Smart Values.
Find out why a field isn't in the list
Formify's field list shows the fields on the space's screens whose type Jira lets apps change. Sprint, Attachment, Jira's Story point estimate and fields added by other apps don't appear there.
To see a custom field's type, a Jira admin can open the list of custom fields in Jira's settings and read the Type column.
If a field you need is missing and you aren't sure why, contact support with the field's type.