Troubleshoot Behaviours

If your behaviour script does not trigger as expected, we recommend checking the following: Is the space a Jira Service Management space? If so, JSM is currently not supported in Behaviours.

logger.info("Debugging : Script for behaviour XXX is running")

You should verify the following:

• Check the behaviour logs for the logging line once you have tried to initiate your behaviour. If the logging line is output, the script is initiating, so it's most likely the case that you have an issue with the contents of your script.
• Ensure the field types you're using in your script are currently supported in our Behaviours Supported Fields and Products.
• Ensure the view you're testing the behaviour on is currently supported in our Behaviours Supported Fields and Products.
• Check that you're using the correct behaviour API methods and syntax for Cloud. If you are migrating from Server/DC, the methods are different.

If you have checked the above and believe your script is correct, please contact the Adaptavist Support team, providing a copy of the script for further assistance.

Please note that our Support SLA does not cover custom scripting, including converting Server/DC scripts to the Cloud. Should you require assistance with this, please contact our Development Services team.

If you set a default Description or default field values based on the work type, you may find that these values remain when changing from the applicable work type to a different work type. The same is true when changing to a different space. This is a native Jira feature to prevent accidental data loss and is not enforced by ScriptRunner.

As REST APIs v3 uses the Atlassian Document Format (ADF) for fields like Comments, Description, Environment and Text Field (multi-line), you cannot clear the Description field using plain text methods like getFieldById("description").setValue("") or getFieldById("description").setValue(null).

Instead, you'll need to set or clear the field using the ADF builder and generate the required ADF format. For example, if you enter and then remove the content in the builder, it will show you the ADF structure for an empty field.

Here's an example of how to clear the Description field using an ADF body, which you may find helpful as a reference:

// Clear the Description field
getFieldById("description").setValue({
 "version": 1,
 "type": "doc",
 "content": []
})

You may also find mapping your Behaviours to all spaces or all work types helpful. Additionally, you may need to add a condition to check the space key or work type and then update or clear the Description field.

Atlassian's new transition experience in Jira is being permanently rolled out in April 2025. As a consequence, how your Jira expressions ( conditions and validators) work will change. Check out our Breaking Changes section for more information.

let variable = "banana";
let fieldId = null;
if (variable == "banana") {
 fieldId = "customfield_10185"; //Number select list
}
 else if (variable == "apple") {
 fieldId = "customfield_10038"; //select list field
}
console.log("variable"+variable)
console.log("fieldId"+fieldId)
 
const field = getFieldById(fieldId);
field.setRequired(true);

The Behaviours feature does not support dynamically selecting the Affected Field within the script. The issue in the example script above is the dynamic usage of the getFieldById method. Due to Atlassian's constraints, we must automatically calculate and pass the affected fields based on the script. However, as the script is dynamic, our parser cannot identify which fields are affected.

getFieldById("customfield_10185").setRequired(true);

const field = getFieldById(fieldId);
field.setRequired(true);

• Take our ScriptRunner Tour.
• See our Example Scripts for Behaviours.
• Behaviours Limitations.
• Behaviours Supported Fields and Products.