What are Behaviours?

Behaviours give you more control over fields in Jira. A field configuration customizes how fields behave, based on the issue operation screen they appear on. However, a behaviour in ScriptRunner allows you to take that field customization further, defining how fields behave for issues in a given project or issue context.

How to use Behaviours

Behaviours let you extend the standard field configuration options available in Jira, and give you the power to use contextual information like current field values, workflow step name, or user details as conditional logic.

You can create behaviours to:

• Prefill/preformat a template for the Description field for users to follow when an issue is created.

• Make a custom field read-only depending on the workflow state.

• Dynamically make calls to external data sources based on user selections when an issue is created.

• Hide a custom field depending on the workflow state, or the value of another custom field.

Behaviours give you more options to customize how fields in Jira behave, so you can show/hide additional fields when a particular option is selected. For example, you give users the option to select a checkbox when they do not know their SEN (Support Entitlement Number). You can set up a behaviour to show additional fields when this checkbox is selected, to collect the information required to identify them.

Alternatively, you might want to use a behaviour to control what information certain users can edit or view. For example, as a project manager, you may want full control over which issues go into a sprint. Using behaviours, you can make the Sprint field read-only for anyone except users in the Project Managers role, ensuring only project managers can add issues to sprints.

Data Residency

Data residency gives organizations more control over their data by ensuring their user-generated content is stored within the US or the EU. Currently, we do not support data residency on the ScriptRunner for Jira Cloud Behaviours feature.