> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/jira-administrator/supported-fields-per-view.md).

# Supported Fields per View

Which Jira fields UI Modifications support on each view - Global Issue Create, Issue View, Issue Transition and JSM Request Create, plus the Agent views.

This page lists which fields are available to UI Modifications rules on each view type. Support depends on the underlying UI Modifications platform API and varies by field type and view.

The table below covers the four standard views. The three JSM Agent View types (Global Issue Create, Issue View, and Issue Transition, all Agent view) are not listed as separate columns because their field support is the same as the corresponding standard view - see [JSM Agent View notes](#jsm-agent-view-notes).

## Field operations

The platform exposes seven operations that rules use:

| Operation                | Used by                                                                                                                  |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| **setVisible**           | Show field                                                                                                               |
| **setRequired**          | Make field required                                                                                                      |
| **setValue**             | Pre-fill field, Change field value, Enable self-assignment only (reverts invalid assignee selections)                    |
| **setReadOnly**          | Lock field                                                                                                               |
| **setOptionsVisibility** | Hide field options, Hide issue types                                                                                     |
| **setDescription**       | Use description, Lock field (optional description override), Enable self-assignment only (optional description override) |
| **setName**              | Use name                                                                                                                 |

Not every field supports every operation, and support varies by view. Individual rule pages list the specific exceptions that apply to that rule.

## Support table

The table below shows which fields are accessible via UI Modifications on each view. A field marked as supported can be used in rules on that view. Fields not listed here cannot be targeted by any rule.

Fields that are marked as supported can also be used in **field conditions** on the corresponding view. In addition, some fields are available exclusively in conditions - see [Condition-only fields](#condition-only-fields) below.

| Field             | Global Issue Create | Issue View | Issue Transition | JSM Request Create |
| ----------------- | ------------------- | ---------- | ---------------- | ------------------ |
| **System fields** |                     |            |                  |                    |
| Affects versions  | Yes                 | Yes        | Yes              | No                 |
| Assignee          | Yes                 | Yes        | Yes              | No                 |
| Components        | Yes                 | Yes        | No               | No                 |
| Description       | Yes                 | Yes        | Yes              | Yes                |
| Due date          | Yes                 | No         | No               | Yes                |
| Fix versions      | Yes                 | Yes        | Yes              | No                 |
| Issue type        | Yes                 | No         | Yes              | No                 |
| Labels            | Yes                 | Yes        | Yes              | Yes                |
| Original estimate | No                  | Yes        | Yes              | No                 |
| Parent            | Yes                 | Yes        | Yes              | No                 |
| Priority          | Yes                 | Yes        | Yes              | Yes                |
| Reporter          | Yes                 | Yes        | Yes              | No                 |
| Resolution        | No                  | No         | Yes              | No                 |
| Status            | No                  | Yes        | No               | No                 |
| Summary           | Yes                 | Yes        | Yes              | Yes                |
| Target start      | Yes                 | No         | No               | No                 |
| Target end        | Yes                 | No         | No               | No                 |
| **Custom fields** |                     |            |                  |                    |
| Cascading select  | Yes                 | Yes        | Yes              | Yes                |
| Checkboxes        | Yes                 | Yes        | Yes              | No                 |
| Date picker       | Yes                 | Yes        | Yes              | Yes                |
| Date time         | Yes                 | Yes        | Yes              | Yes                |
| Multi select      | Yes                 | Yes        | Yes              | Yes                |
| Multi user picker | Yes                 | Yes        | Yes              | No                 |
| Number            | Yes                 | Yes        | Yes              | Yes                |
| Paragraph         | Yes                 | Yes        | Yes              | Yes                |
| People            | Yes                 | Yes        | No               | No                 |
| Project picker    | Yes                 | Yes        | Yes              | No                 |
| Radio buttons     | Yes                 | Yes        | Yes              | No                 |
| Single select     | Yes                 | Yes        | Yes              | Yes                |
| Text field        | Yes                 | Yes        | Yes              | Yes                |
| URL               | Yes                 | Yes        | Yes              | No                 |
| User picker       | Yes                 | Yes        | Yes              | Yes                |

## JSM Agent View notes

Field support on Global Issue Create (Agent view), Issue View (Agent view), and Issue Transition (Agent view) mirrors the corresponding standard Jira view field-for-field.

On Issue View (Agent view), Atlassian does not apply UI Modifications to fields that are part of the request create form. See [Limitations](https://docs.forgappify.com/field-rules/jira-administrator/limitations.md#jsm-agent-view) for details.

## JSM Request Create notes

The JSM Request Create view has more limited field support than the standard Jira views. Several system fields (Assignee, Components, Reporter, Parent, version fields) are not accessible via UI Modifications on the portal. Within the supported custom field types, some operations may still be unavailable - check each rule's documentation for the specific JSM exceptions.

Fields that appear on a JSM request form but are not in the table above cannot be targeted by any rule. The set of fields accessible on the portal is determined by the platform.

## Issue Transition notes

On Issue Transition and Issue Transition (Agent view), fields do not need to be placed on the transition screen for use in **field conditions**. Status and Resolution values are fetched from the issue in the background if they are not present on the screen. This allows transition rules to evaluate the issue's current state without requiring those fields on every transition screen.

For rule **actions** (setVisible, setRequired, setValue, etc.), the field must be present on the transition screen. Rules targeting a field that is not on the screen are silently skipped.

## Condition-only fields

Some fields are available exclusively for use in conditions and cannot be targeted by rule actions:

**Project** - always available in conditions on Global Issue Create, Issue View, Issue Transition, and their Agent view equivalents, even though the Project field itself is not listed in the table. Not available as a condition on JSM Request Create.

**Issue Type** - always available as a condition field on Global Issue Create, Issue View, Issue Transition, and their Agent view equivalents, read from the screen context. On Global Issue Create and Issue Transition (including Agent view) it also appears in the table above, meaning rules can target it directly. On Issue View the platform does not allow targeting Issue Type via rule actions, but it remains usable in conditions. Not available as a condition on JSM Request Create.

**Request Type** - available as a condition field on JSM Request Create and on all three JSM Agent View types. It is not listed in the support table above and cannot be targeted by rule actions. Use it to apply different rules to different request types on the same portal or Agent view project.

## Detailed operation support

Each rule's documentation page lists exactly which field types support that rule's specific operation, broken down by view type. For full detail on what is supported where:

* [Show field - Supported fields](https://docs.forgappify.com/field-rules/rules/show-field.md#supported-fields)
* [Make field required - Supported fields](https://docs.forgappify.com/field-rules/rules/make-field-required.md#supported-fields)
* [Pre-fill field - Supported fields](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md#supported-fields)
* [Change field value - Supported fields](https://docs.forgappify.com/field-rules/rules/change-field-value.md#supported-fields)
* [Lock field - Supported fields](https://docs.forgappify.com/field-rules/rules/lock-field.md#supported-fields)
* [Hide field options - Supported fields](https://docs.forgappify.com/field-rules/rules/hide-field-options.md#supported-fields)
* [Use name - Supported fields](https://docs.forgappify.com/field-rules/rules/use-name.md#supported-fields)
* [Use description - Supported fields](https://docs.forgappify.com/field-rules/rules/use-description.md#supported-fields)
