Skip to main content

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​

FieldValueOptionsIn conditionsScreens and rules that differ
SummaryYesNoYesNo Required rule: Jira always requires it. On the work item view, Read-only only.
DescriptionYesNoYesOn the work item view, no Description rule.
Issue typeYesYesYesValue and Options rules only, in the Create dialog and transition dialogs.
PriorityYesYesYesOn the work item view, no Description rule.
AssigneeYes, also smart valuesNoYes
ReporterYes, also smart valuesNoYes
LabelsYes, also smart valuesNoYes
Due dateYes, also smart valuesNoNoCreate dialog only.
ComponentsNoNoNoCreate dialog and work item view.
Fix versionsNoIn transition dialogsNo
Affects versionsNoNoNo
ParentNoNoNo
Original estimateNoNoNoWork item view and transition dialogs.
ResolutionNoNoNoTransition dialogs only. No Required rule.
StatusNoNoIts own conditionNo rules. The Issue status condition reads it on the work item view and in transition dialogs.

Check a custom field type​

Field typeValueOptionsIn conditionsScreens that differ
Text field (single line)YesNoYes
ParagraphNoNoNo
URLYesNoYes
NumberYesNoYes
Select listNoYesYes
Radio buttonsNoYesYes
Multi-select listYesYesYes
CheckboxesYesYesYes
Cascading selectYesNoNo
Date pickerYes, also smart valuesNoNo
Date time pickerYes, also smart valuesNoNo
User pickerYes, also smart valuesNoNo
Multi-user pickerYes, also smart valuesNoNo
PeopleNoNoNoCreate dialog and work item view.
Project pickerNoNoNo
Target start, Target endNoNoNoCreate 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.