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

Luca Andreatta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 11, 2021

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
Ram Kumar Aravindakshan _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 11, 2021

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,

Ram

Luca Andreatta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 12, 2021

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:

Firefox_Screenshot_2021-05-12T07-11-00.630Z.png

Luca Andreatta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 12, 2021

Hi Ram,

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

The official guide (https://confluence.atlassian.com/jiracore/upgrading-jira-server-976161476.html) 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(cf.name, "Il "+customFieldName+" deve avere "+length+" caratteri.")

As you can see this is not true:

Firefox_Screenshot_2021-05-12T08-22-50.563Z.png

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

John Chin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2021
Like Luca Andreatta likes this
Luca Andreatta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 17, 2021

Many thanks John, I will wait for the bugfix.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events