Behaviours Supported Fields and Products

Supported Jira Products

Jira Product	Supported Capability	Supported on Cloud
Jira	Company-managed projects
Jira	Team-managed projects
Jira Service Management

Supported Fields

Fields/Methods Not Supported

We continually strive to support the functionality provided by Atlassian. Here's a link to Atlassian's UI Modifications guide, where you can find further information.

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.

Wildcard Limitations

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

Modifications may only be made on the supported fields depending on your selected view, as outlined in the Create, Issue and Transition view sections below:

Create View Supported Fields

Field/methods	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
radio buttons
reporter
single select
summary
target start
target end
text field
url
user picker

Issue View Supported Fields

Hidden fields

When the text (single), select list (single and multiple), checkbox, radio and number fields are set to read only but have no value in Issue View, they will be hidden.

Field/methods	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
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	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
radio buttons
reporter
resolution
single select
text field
url
user picker