ScriptRunner - Behaviour - Error does not prevent to save issue

Since we migrated from JIRA 6.3.12, Scriptrunner 3.1.4 to JIRA 7.1.7, Scriptrunner 4.3.5, our behavior scripts that validate field values do not work correctly anymore.

With code

formField.setError ("Some error message.")

I still see the red message below the field in case an invalid value is entered in the field, but I can save the issue without any further message. The "wrong" value is stored in the issue.

Do I miss something ?

Something changed ?

3 answers

This widget could not be displayed.

Nothing changed, and we got your support ticket too. Can you check for javascript errors by pressing F12, and make sure you click the "Preserve Log" checkbox so that the log is not erased on navigation.

This widget could not be displayed.

Hi, I can't see any javascript errors in the console.

In the Behavior, I have several fields defined, they all launch a (their proper groovy) script.

I added debug logging in all the scripts, and can so track what script is launched. When a field is changed, the script attached to that field is launched, and no other one. If an error is entered in the field, the error message is set (see code above), and in the User Interface I see correctly the error message appearing. Then, when I click "Save", no behavior scripts are launched anymore, but the issue is saved with the erroneous values for the field.

How to find out what goes wrong ?

This widget could not be displayed.

Hi, I think (!!!) I figured out the case (one of the cases ???) where it goes wrong.

I have a behavior on field Fix Versions, that checks that there is only one version selected in the field, otherwise it raises an error. This works fine, the error message is shown correctly under the field

I also have an Initializer Function in the same behavior, that does several things, among setting the required flag for the field Fix Versions (I have to do this as the flag depend the current state of the issue):

FormField fldFixVersion = getFieldById("fixVersions")
if (...) {
else {

When I comment out just these lines in the initialize function, everything goes fine.

I have the same problem with all fields where I do the combination of

  • setting some flags in the Initializer Function (required, hidden, ..)
  • do a validation on field change

The validation is done and in case the correct error message is shown. But I can save the issue, also with errors in fields.

Seems to be some kind of undesirable interaction - I have created a bug report at possible workaround on that ticket.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

49 views 1 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you