Supported Fields per View

Support for UI Modifications varies slightly depending on the view. To simplify this, we’ve consolidated all supported fields into a single table. The second column indicates whether a field is a System field (provided by Jira) or a Custom field type (created by a Jira Administrator).

Each field supports a different set of operations (e.g., setRequired, setVisible, etc.). For a detailed breakdown of supported operations per field and view, please refer to Atlassian’s official UI Modifications API documentation.

Field type	System/Custom	Global Create Issue	Issue View	Issue Transition
affects versions	System
assignee	System
cascading select	Custom
components	System
checkboxes	Custom
date picker	Custom
date time picker	Custom
description	System
due date	System
fix versions	System
issue type	System
labels	System
multi select	Custom
multi user picker	Custom
number	Custom
original estimate	System
paragraph	Custom
parent	System
people	Custom
priority	System
project picker	Custom
radio buttons	Custom
reporter	System
resolution	System
single select	Custom
status	System
summary	System
target start	System
target end	System
text field	Custom
url	Custom
user picker	Custom

Supported Fields in Field Conditions

Field Conditions in Field Rules rely on the UI Modifications API to retrieve field values. This means:

• A field must be of one of the supported types listed above.

• A field must be supported on the current view in order for its value to be available.

• In most views, the field must also be included on the screen associated with that view.

If these requirements are not met, the condition may not be able to evaluate the field’s value.

Additional Fields Supported in Field Conditions

• Project – You can use the Project field in Field Conditions even though it is not supported by the UI Modifications (UIM) framework.

Field conditions on Issue Transition View

Based on customer feedback, the limitation that field conditions could only be evaluated against fields present on the screen has been removed for the Issue Transition view. Field conditions are now correctly evaluated during issue transitions even when the fields are not included on the Transition screen.

Previously, this was a significant constraint, as Transition screens are typically designed to display only a subset of issue fields. This enhancement allows you to define powerful rules preconditions without cluttering the Transition screen with additional fields.