-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
jira-trigger: 0.5.1
Jenkins ver.: 2.60.3
java.runtime.name OpenJDK Runtime Environment
java.runtime.version 1.8.0_131-b12
JIRA: v7.3.1
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.
[JENKINS-46787] JIRA Trigger Plugin doesn't map all non-custom Issue objects
Marcus Greville
created issue -
Marcus Greville
made changes -
| Attachment | New: image-2017-09-11-22-52-24-511.png [ 39656 ] | |
| Description |
Original:
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 TESJIRA-204 KEY TESJIRA-204 Now I'll provide some representative working and failing examples to demonstrate the problem. *1. Working example of top level data* + echo SUM Asset 3: Work being completed SUM Asset 3: Work being completed JSON payload: "summary": "Asset 3: Work being completed", !image-2017-09-11-22-17-45-487.png! *2. Working example of nested data* JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, !image-2017-09-11-22-07-49-291.png! + echo ASSIG marcus.greville ASSIG marcus.greville *3. Failing example of top level data* JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", !image-2017-09-11-22-08-11-105.png! + echo 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. |
New:
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 {code:java} echo KEY: ${JIRA_ISSUE_KEY} KEY: TESJIRA-204{code} Now I'll provide some representative working and failing examples to demonstrate the problem. *1. Working example of top level data* {code:java} echo SUM: ${SUM} SUM: Asset 3: Work being completed{code} JSON payload: "summary": "Asset 3: Work being completed", !image-2017-09-11-22-52-24-511.png! *2. Working example of nested data* {code:java} echo ASSIG: ${ASSIG} ASSIG: marcus.greville{code} JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, !image-2017-09-11-22-07-49-291.png! *3. Failing example of top level data* {code:java} echo LV: ${LV} LV:{code} JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", !image-2017-09-11-22-08-11-105.png! 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. |
Marcus Greville
made changes -
| Attachment | Original: image-2017-09-11-22-07-01-673.png [ 39655 ] |
Marcus Greville
made changes -
| Attachment | Original: image-2017-09-11-22-17-24-310.png [ 39652 ] |
Marcus Greville
made changes -
| Description |
Original:
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 {code:java} echo KEY: ${JIRA_ISSUE_KEY} KEY: TESJIRA-204{code} Now I'll provide some representative working and failing examples to demonstrate the problem. *1. Working example of top level data* {code:java} echo SUM: ${SUM} SUM: Asset 3: Work being completed{code} JSON payload: "summary": "Asset 3: Work being completed", !image-2017-09-11-22-52-24-511.png! *2. Working example of nested data* {code:java} echo ASSIG: ${ASSIG} ASSIG: marcus.greville{code} JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, !image-2017-09-11-22-07-49-291.png! *3. Failing example of top level data* {code:java} echo LV: ${LV} LV:{code} JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", !image-2017-09-11-22-08-11-105.png! 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. |
New:
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 {code:java} echo KEY: ${JIRA_ISSUE_KEY} KEY: TESJIRA-204{code} 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", {code:java} echo SUM: ${SUM} SUM: Asset 3: Work being completed{code} !image-2017-09-11-22-52-24-511.png! *2. Working example of nested data* JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, {code:java} echo ASSIG: ${ASSIG} ASSIG: marcus.greville{code} !image-2017-09-11-22-07-49-291.png! *3. Failing example of top level data* JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", {code:java} echo LV: ${LV} LV:{code} !image-2017-09-11-22-08-11-105.png! 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. |
Marcus Greville
made changes -
| Attachment | New: JIRA-webhook-POST-results.zip [ 39670 ] |
Wisen Tanasa
made changes -
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Aswin Achuthan
made changes -
| Description |
Original:
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 {code:java} echo KEY: ${JIRA_ISSUE_KEY} KEY: TESJIRA-204{code} 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", {code:java} echo SUM: ${SUM} SUM: Asset 3: Work being completed{code} !image-2017-09-11-22-52-24-511.png! *2. Working example of nested data* JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, {code:java} echo ASSIG: ${ASSIG} ASSIG: marcus.greville{code} !image-2017-09-11-22-07-49-291.png! *3. Failing example of top level data* JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", {code:java} echo LV: ${LV} LV:{code} !image-2017-09-11-22-08-11-105.png! 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. |
New:
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 {code:java} echo KEY: ${JIRA_ISSUE_KEY} KEY: TESJIRA-204{code} 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", {code:java} echo SUM: ${SUM} SUM: Asset 3: Work being completed{code} !image-2017-09-11-22-52-24-511.png! *2. Working example of nested data* JSON payload (abridged): "assignee": \{ "name": "marcus.greville", }, {code:java} echo ASSIG: ${ASSIG} ASSIG: marcus.greville{code} !image-2017-09-11-22-07-49-291.png! *3. Failing example of top level data* JSON payload: "lastViewed": "2017-09-11T14:06:10.573+1000", {code:java} echo LV: ${LV} LV:{code} !image-2017-09-11-22-08-11-105.png! 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. |
