JIRA Workflow exception

Seeing lot of expectations wondering if this is normal

2013-08-13 09:53:25,336 http-bio-8443-exec-49 ERROR josh.gomez 593x1384x7 f5ynu2 /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 5 from workflow 56028 on issue 'CONT-4275'
[InvalidInputException: [Error map: [{customfield_10722=OSR Version is required.}]] [Error list: [[]]]

Told by support

This looks like an issue with a third party plugin you have installed - Jira Suite Utilities:


If you follow that link there is an issues and support section for the vendor. Somebody may have raised this already with them so they should be able to help you.

3 answers

1 vote

The Jira Suite Utilities has a validator that allows you to make a field mandatory. It works, but unfortunately throws exceptions into the log when a user does something that fails the validation check.

So, it is "normal", but I think we'd all agree it's not desirable behaviour - it should be a simple "fail", not a full java exception. I am pretty sure I've seen an issue logged in the JSU tracker, but I've not got it bookmarked.

I agree throwing full Java exception is extreme over kill. I opened bug with the developer.. THANKS for response

Unfortunately, this is the way JIRA validators work: the must raise an Exception to signify to JIRA that the validation failed (validate is a void function)

Is there any logging levels that can resolve this in Jira configuration?

There's nothing to resolve - you get an exception in the log if validation fails.

If you're getting other exceptions, then more logging isn't going to tell you a lot - you need to investigate the exception.

If you really want to get rid of this ERROR in your logs, you can deactivate logging for atlassian.jira.workflow.OSWorkflowManager entirely (log level=NONE). But the consequence is that you will never see any error raised by this class anymore, which might hide other problems.

Still seems that the java error that flags the plugin that requrment was not meet should have a diffrenet logging level so you do not spam your log files. We have good number of required fields in our workflwos

This makes very hard to parse the log files for "real" errors

Absolutely, it's a pain in the neck having to do it like this. A validator shouldn't have to throw exceptions just to say "no, the data is wrong"

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,772 views 18 21
Read article

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