I have script validation on create transition not working properly on Jira Service Desk Portal.

I have a validation on Cascade select i.e second level of field in mandatory. it is throwing an error message while creating a ticket in JIRA but not working while creating from JIRA service desk(Customer portal)

2 answers

1 vote

It's a bug in JSD, it fails to show validation errors. Maybe: https://jira.atlassian.com/browse/JSD-1638

1 vote

There currently seems to be a JIRA service desk bug affecting workflow validators. Note that using the following will not work:

import com.opensymphony.workflow.InvalidInputException
throw new InvalidInputException("In Progress", "This won't work")

Resulting in a error message being shown and an exception in the logs:

17-Mar-2016 02:18:26.669 WARNING [http-nio-8080-exec-5] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira-dev.cloud.twc.net/rest/servicedesk/1/customer/pages/portal/35/create/176, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
2016-03-17 02:18:31,508 http-nio-8080-exec-5 ERROR E030362 138x3704x1 6xsaf5, /servicedesk/customer/portal/35/create/176 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: messages must have at least one entry
java.lang.IllegalArgumentException: messages must have at least one entry
	at com.atlassian.pocketknife.api.commons.error.ErrorBuilder.buildSingleError(ErrorBuilder.java:107)
	at com.atlassian.pocketknife.api.commons.jira.ErrorCollectionHelper.error(ErrorCollectionHelper.java:22)
	at com.atlassian.servicedesk.internal.feature.customer.request.CustomerRequestManager.com$atlassian$servicedesk$internal$feature$customer$request$CustomerRequestManager$$createCustomerRequest(CustomerRequestManager.scala:109)

But interestingly as a workaround this will work:

import com.opensymphony.workflow.InvalidInputException
throw new InvalidInputException("This will work")

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

242 views 1 18
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