Behaviours Supported Fields and Products
Supported Jira products
| Jira Product | Supported Capability | Supported on Cloud |
|---|---|---|
Jira | Company-managed projects |
|
Team-managed projects |  | |
Jira Service Management |  |
Behaviours is only supported in the Create view for Business company-managed projects.
Supported Jira view-specific limitations
| View | Project type |
|---|---|
| Jira global issue create | Company-managed Team-managed |
| Jira issue view | Company-managed Team-managed |
| Jira issue transition | 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 projects or All issue types only; due to an Atlassian limitation, both options cannot be chosen simultaneously.
Using the 'All Projects' field on a behaviour means only 1 context is used for projects. If it is used with several Issue Types, then this 1 context is multiplied by the number of issue 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 |
|---|---|---|
Project | All Projects (100 Projects) | 1 |
Issue Type/s | Story, Bug, Task | 3 |
View Types | 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. 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
| 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
Hidden fields
On 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 behavior 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 | | | | | | | | |
| priority | | | | | | | | |
| project picker | | | | | | | | |
| radio buttons | | | | | | | | |
| reporter | | | | | | | | |
| single select | | | | | | | | |
| status | | | | | | | | |
| summary | | | | | | | | |
| text field | | | | | | | | |
| url | | | | | | | | |
| user picker | | | | | | | |
|
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
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 | | | | | | | | |
| text field | | | | | | | | |
| url | | | | | | | | |
| user picker | | | | | | | |
|