It seems the excellent jira-trigger plugin isn't able to map all non-custom Issues attributes to parameters.
Webhooks are working and I have successfully resolved my JIRA_ISSUE_KEY
Now I'll provide some representative working and failing examples to demonstrate the problem.
1. Working example of top level data**
"summary": "Asset 3: Work being completed",
2. Working example of nested data
JSON payload (abridged):
3. Failing example of top level data
When an item fails to resolve this gets posted to the logs -
Sep 11, 2017 6:55:47 PM SEVERE java_util_logging_Logger$log$2 call
Hit JiraTriggerException! (jira-trigger-plugin has failed to translate this exception to a human friendly error message, please report a bug).
com.ceilfors.jenkins.plugins.jiratrigger.JiraTriggerException: Class: ParameterErrorCode, Name: FAILED_TO_RESOLVE, Code: 1, Attributes: [:]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Full trace is attaced - jira_trigger_plugin_stack_trace.txt
The item failures have no apparent pattern to my eye.
I will mention here for completeness sake the CustomFields I tested would not resolve either.
I believe the issue is likely the same as https://issues.jenkins-ci.org/browse/JENKINS-39766
If there is anything other detail I can provide let me know.