Behaviours Supported Fields and Products
Jira terminology changes
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 |  |
Behaviours are only supported in the Create view for Business company-managed spaces.
Supported Jira view-specific limitations
| View | Space type |
|---|---|
| Jira global issue create (Create view type) | Company-managed Team-managed |
| Jira issue view (View/Edit view type) | Company-managed Team-managed |
| Jira issue transition (Transition view type) | Company-managed |
Refer to Atlassian's Jira UI modifications documentation for more details.
Supported fields
Behaviours mapping wildcard limitations
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.
Using the 'All spaces' field on a behaviour means only 1 context is used for spaces. If it is used with several Work Types, then this 1 context is multiplied by the number of work types selected. If we enable this behaviour for multiple view types, this value is also multiplied by the number of view types. For example:
Field | Selected | Contexts |
|---|---|---|
Space | All Spaces (100 spaces) | 1 |
Work Type/s | Story, Bug, Task | 3 |
Jira Views | Issue Create, Issue View | 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.
System Fields & Custom Fields
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 type Labels. 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 | System Field Type | setName getName | setDescription getDescription | setVisible isVisible | setValue getValue | setReadOnly isReadOnly | setRequired isRequired | setOptionsVisibility getOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| 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)
Hidden fields
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 | System Field Type | setName getName | setDescription getDescription | setVisible isVisible | setValue getValue | setReadOnly isReadOnly | setRequired isRequired | setOptionsVisibility getOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| 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 | | | | | | | |
|
Story Points field does not perform in the same way as a regular number field
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)
Transition view supported fields (Transition view type)
Atlassian's New Transition Dialog
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 | System Field Type | setName getName | setDescription getDescription | setVisible isVisible | setValue getValue | setReadOnly isReadOnly | setRequired isRequired | setOptionsVisibility getOptionsVisibility |
|---|---|---|---|---|---|---|---|---|
| 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 | | | | | | | |
|