Suggestion Summary

Currently while using the following module: 

jira:jqlFunction

Whenever a JQL search is made using the custom Function, there is no pre-invocation argument validation, meaning, that a user can provide incorrect number of arguments and still the app is invoked, consuming resources, and only in the execution time, Jira identifies that the number of arguments is invalid.

While it's possible as a workaround, check the number of arguments in the request, in the end it still requires the app being invoked and resources being used to check if the correct number of arguments are valid.

Having Jira check it before actually invoke the app's backend function will reduce the app's consume.