Behaviours Supported Fields and Products
As noted in our March 2026 release note, ScriptRunner for Jira Cloud is aligning with Jira's updated terminology across the app UI and documentation.
Some Atlassian documentation - particularly the Jira UI modifications guide referenced throughout this page - still uses the previous terminology. As a result, this page currently reflects that older terminology with only minimal updates, and will be revised in due course.
Supported Jira products
| Jira Product | Supported Capability | Supported on Cloud | |
|---|---|---|---|
| Jira | Company-managed spaces | ||
| Team-managed spaces | |||
| Jira Service Management |
Supported Jira view-specific limitations
| View | Space type |
|---|---|
| Jira global issue create (Create view type) | Company-managedTeam-managed |
| Jira issue view (View/Edit view type) | Company-managedTeam-managed |
| Jira issue transition (Transition view type) | Company-managed |
Supported fields on Jira
You can select the wildcard option for either All spaces or All work types only; due to an Atlassian limitation, both options cannot be chosen simultaneously.
| Field | Selected | Contexts |
|---|---|---|
| Space | All Spaces (100 spaces) | 1 |
| Work Type/s | Story, Bug, Task | 3 |
| Jira Views | Issue Create, Issue View(Create, View/Edit view types) | 2 |
| Total | 6 |
Developing Behaviours on Cloud and adding more functionality to this feature remains a high priority for the ScriptRunner team! Behaviours can be applied to Sub-tasks and the supported fields outlined below for the Global Issue Create, Issue, and Transition views (Create, View/Edit, Transition view types). We continually strive to support the functionality provided by Atlassian. For more information, please refer to Atlassian's UI Modifications guide.
Modifications can only be made to supported fields, depending on your selected view, as outlined in the Create, Issue, and Transition view sections below.
In Behaviours, some Jira-native system fields can be custom field types. An example of this is the Labels field, which is a Jira-native system field. Only Jira-native system fields are supported, so your Behaviours may not function correctly if you have created a custom field of typeLabels. System field types are identified in each of the Supported Fields tables below, while custom field types are marked with a 
.
Create view supported fields (Create view type)
| Field/methods | SystemField Type | setNamegetName | setDescriptiongetDescription | setVisibleisVisible | setValuegetValue | setReadOnlyisReadOnly | setRequiredisRequired | setOptionsVisibilitygetOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| affects version | ||||||||
| assignee | ||||||||
| cascading select | ||||||||
| components | ||||||||
| checkboxes | ||||||||
| date picker | ||||||||
| date time picker | ||||||||
| description | ||||||||
| due date | ||||||||
| fix versions | ||||||||
| issue type | ||||||||
| labels | ||||||||
| multi select | ||||||||
| multi user picker | ||||||||
| number | ||||||||
| paragraph | ||||||||
| parent | ||||||||
| people | ||||||||
| priority | ||||||||
| project picker | ||||||||
| radio buttons | ||||||||
| reporter | ||||||||
| single select | ||||||||
| summary | ||||||||
| target start | ||||||||
| target end | ||||||||
| text field | ||||||||
| url | ||||||||
| user picker |
Issue view supported fields (View/Edit view type)
On the Issue view, fields with no value are automatically hidden when they are set to read-only. For example, empty read-only date picker, text (single), select list (single and multiple), checkbox, radio, and number fields are hidden. This is the default behaviour when the user does not have permission to edit the issue.
| Field/methods | SystemField Type | setNamegetName | setDescriptiongetDescription | setVisibleisVisible | setValuegetValue | setReadOnlyisReadOnly | setRequiredisRequired | setOptionsVisibilitygetOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| affects versions | ||||||||
| assignee | ||||||||
| cascading select | ||||||||
| components | ||||||||
| checkboxes | ||||||||
| date picker | ||||||||
| date time picker | ||||||||
| description | ||||||||
| fix versions | ||||||||
| labels | ||||||||
| multi select | ||||||||
| multi user picker | ||||||||
| number | ||||||||
| original estimate | ||||||||
| paragraph | ||||||||
| parent | ||||||||
| people | ||||||||
| priority | ||||||||
| project picker | ||||||||
| radio buttons | ||||||||
| reporter | ||||||||
| single select | ||||||||
| status | ||||||||
| summary | ||||||||
| text field | ||||||||
| url | ||||||||
| user picker |
The Story Points field must not be handled as a generic supported Number field. In Jira Cloud, Story Points is a Jira-managed special field, and Jira does not reliably enforce read-only behavior for it in the Issue View.
Supported views for issue view
Behaviours configured to run on the Issue View are triggered when accessed through one of the views outlined below, which are highlighted with example images:
full page issue
board issue
backlog issue
list issue
Issues issue
search issue (global search)
image href="media/search-issues.png" width="600" placement="break"/>
Transition view supported fields (Transition view type)
Behaviours on transition view run only in the new Issue transition dialog, as defined by Atlassian's UI Modifications API. If this has not been enabled for your instance, then Behaviours on transition view will not work.
| Field/methods | SystemField Type | setNamegetName | setDescriptiongetDescription | setVisibleisVisible | setValuegetValue | setReadOnlyisReadOnly | setRequiredisRequired | setOptionsVisibilitygetOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| affects version | ||||||||
| assignee | ||||||||
| cascading select | ||||||||
| checkboxes | ||||||||
| date picker | ||||||||
| date time picker | ||||||||
| description | ||||||||
| fix versions | ||||||||
| issue type | ||||||||
| labels | ||||||||
| multi select | ||||||||
| multi user picker | ||||||||
| number | ||||||||
| original estimate | ||||||||
| paragraph | ||||||||
| parent | ||||||||
| priority | ||||||||
| project picker | ||||||||
| radio buttons | ||||||||
| reporter | ||||||||
| resolution | ||||||||
| single select | ||||||||
| summary | ||||||||
| text field | ||||||||
| url | ||||||||
| user picker |
Supported fields on JSM
Developing Behaviours on Cloud and adding more functionality to this feature remains a high priority for the ScriptRunner team! Behaviours can be applied to Sub-tasks and the supported fields outlined below for the Request Create Portal on Jira Service Management. We continually strive to support the functionality provided by Atlassian. For more information, please refer to Atlassian's UI Modifications guide.
Modifications can only be made to supported fields, depending on your selected view, as outlined in the section below.
In Behaviours, some Jira-native system fields can be custom field types. An example of this is the Labels field, which is a Jira-native system field. Only Jira-native system fields are supported, so your Behaviours may not function correctly if you have created a custom field of typeLabels. System field types are identified in each of the Supported Fields tables below, while custom field types are marked with a .
Request create portal (Preview)
| Field/methods | SystemField Type | setNamegetName | setDescriptiongetDescription | setVisibleisVisible | setValuegetValue | setReadOnlyisReadOnly | setRequiredisRequired | setOptionsVisibilitygetOptionsVisibility | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| cascading select | |||||||||||
| date picker | |||||||||||
| date time picker | |||||||||||
| description | |||||||||||
| due date | |||||||||||
| labels | |||||||||||
| multi select | |||||||||||
| number | |||||||||||
| paragraph | |||||||||||
| priority | |||||||||||
| single select | |||||||||||
| summary | |||||||||||
| text field | |||||||||||
| user picker |