Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Custom Validator exception doesn't work on Jira 8.16.1 in Customer Portal


I just upgraded Jira to version 8.16.1, but the custom ScriptRunner validator that I wrote doesn't work anymore, the error message doesn't appear in the Customer Portal.

I tried also with a Simple Scripted Validator linking it to the description, but the error is the same.

import com.opensymphony.workflow.InvalidInputException

throw new InvalidInputException( "ERROR MESSAGE.")


1 answer

1 accepted

0 votes
Answer accepted

Hi @Luca Andreatta,

If you intend to use the Simple Scripted Validator, you do not need to return the InvalidInputException. It only requires a boolean response, i.e. something like:

issue.projectObject.key == 'XYZ'

If you intend to use the InvalidInputException, you should use the Custom Script Validator instead.

Could you please paste a print screen of your validator configuration for more information?

Thank you and Kind Regards,


Hi Ram,

it doesn't work also with Simple Scripted Validator and the configuration is very simple, so I don't think that this could be the problem.

I checked instead the version of Jira Service Desk and I saw that it is still an old one, but I don't see any way to upgrade it as written in the official guides:


Hi Ram,

I upgraded manually Jira Service Desk to Jira Service Management 4.16.1.

The official guide ( wasn't right for me.

Now things got better, but I still have a problem because the error message now appears on the top of the screen, but there is an added message that the custom field has not been found:

The field with ID Cod. OPEC is required on screen but it's been deleted.

This is how I threw the Exception (cf is the custom field object from the issue itself):

throw new InvalidInputException(, "Il "+customFieldName+" deve avere "+length+" caratteri.")

As you can see this is not true:


I know that I can remove the customfield name parameter from the InvalidInputException constructor, but maybe I'm doing something wrong.

Like Luca Andreatta likes this

Many thanks John, I will wait for the bugfix.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

[Upcoming Webinar] Atlassian Cloud: Marketplace App Availability & Security

If you’re looking to migrate to Atlassian Cloud but feel unsure about what that means for your apps, we hear you. So, we’re planning a webinar this January to discuss topics related to our Cloud Mark...

578 views 0 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you