There are huge errors when requiring fields in workflows. This seems to be directly related to the Jira Suite Utilities plugin since it is using that class for that validation for the fields causing issues.
I have attached both the XML for one of the workflows and the dump from the logs for the error.
Let me know if any other information is needed. Thanks.
I see what you need now. Have a look at https://answers.atlassian.com/questions/40838/how-to-avoid-invalidinputexception-stacktrace-in-log-using-custom-validators
It is JIRA who is printing the error to logs and plugins cannot handle it.
I understand that it is requiring the field, however, i don't agree that if someone didn't fill in that field, there should be 169 lines written to my logs. The problem i am reporting is that this is throwing an error and stack trace into my logs for correct functionality.
I would like to know how to keep using the plugin, while also keeping my logs clean. Thanks.
That is just the way the plugin has been implemented. Sometimes it is really important to know what happens during a transaction. Apart of your use case, where the error simply reports what you expect, input for a given field is missing, in most cases it is there to tell us that the admin misconfigured something.
Please have a look at the link below, you may file a new issue, like an improvement, to no longer print out the whole stack trace to the log, but instead only the really important information:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG