Hi Wisen,

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

echo KEY: ${JIRA_ISSUE_KEY}
KEY: TESJIRA-204

Now I'll provide some representative working and failing examples to demonstrate the problem.

1. Working example of top level data**

JSON payload:

"summary": "Asset 3: Work being completed",

echo SUM: ${SUM}
SUM: Asset 3: Work being completed

2. Working example of nested data

JSON payload (abridged):

"assignee": {
    "name": "marcus.greville",
},

echo ASSIG: ${ASSIG}
ASSIG: marcus.greville

3. Failing example of top level data

JSON payload:

"lastViewed": "2017-09-11T14:06:10.573+1000",

echo LV: ${LV}
LV:

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)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

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.

Regards.