Search Results

Overview

Behaviours allow you to change how fields behave on issue create or update screens. Use this script to populate the values of a new issue with the values of an issue selected in an single-select issue picker field.

Example

As a support engineer, I create development issues associated with problems reported by users. Some field values are replicated between the created development issue and the user request. This script allows me to set the values automatically, saving me the time of manually copying it across.

Good to Know

• Associate this script with a single-select issue picker field.

Overview

Behaviours allow you to change how fields behave on issue Create or Update screens. Use this script to restrict the available link values on the Linked Issues field inside an issue Create or Update screen.

Example

As a project manager, I want to limit the available issue link types for issues in a specific project so that I can easily create and maintain JQL filters to find issues with certain link types. I can use this script to restrict the link type options in the Create or Update form of an issue, to only those I have approved. Limiting the link types used, and therefore ...

Overview

Behaviours allow you to change how fields behave on Create Issue or Update Issue screens. Set the default option on a cascading-select custom field using this script in a ScriptRunner Behaviour.

Example

As a project manager, I want to make it easier for my team to fill out Create Issue and Update Issue screens. For example, I have a Product Project field, and I want to specify the most commonly selected option (SR4JS, Support) as the default value. I can use this script to set the default for this field to be SR4JS (Product), Support (Project), saving time and effort for my team.

Good to Know

• Set ...

Overview

Behaviours allow you to change how fields behave on issue Create or Update screens. Scripts can be associated with a field (executed when the field changes) or as an initialiser (executed once the form is opened).

Using this script, you can inherit the value of a multi-user picker field from a parent issue in the sub-task create form, meaning the default value set in the sub-task creation form is taken from the parent issue.

Example

As an admin, I want to suggest users to create sub-tasks with some of the same field values as their parent issue, for example, a multi-user picker field for tracking stakeholders ...