We are getting this error constantly now out of the blue with one of our JMWE Post-Functions, after having this working perfectly fine before;
Set field value - internal-error - Cannot read property 'match' of null
ignoreEmptyValue:false
conditionalExecution:false
sendNotifications:false
createMissingValues:false
valueIsJSON:false
_needsRefresh:true
value:"{{ issue | sprints("active") | last | field("id") }}"
appendValues:false
_modified:"2019-06-13T11:16:22.189Z"
copyOnlyIfNotSet:true
fieldId:"customfield_10007"
runAsType:"addonUser"
Any ideas why this could have suddenly broke/changed on our workflow? :(
If the destination field (customfield_10007) is the Sprint field, then this error will happen if the current issue doesn't belong to any active Sprint, because you're basically setting the spring field to [null]
Instead of logging an error, this should in fact clear the Sprint field. This is a JMWE bug that will be fixed in the next version.
In the meantime, you can avoid these errors by using Conditional Execution with this conditional execution script:
{{ issue | sprints("active") | last | field("id") }}
Thanks for your response David!
And apologies, only just seen your comment now (guess I have my email notifications turned off or something).
I'll continue to keep an eye on the error log but hopefully everything is all good now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.