Different reasons why you are getting processor exception errors are possible:
- JIRA configuration has been changed and now script could not be executed - usually it happens in case the script was working fine before, and now you are getting the error
- The Groovy semantics is wrong - usually, the error occurs on the first sync.
To fix the error, you should get a clear understanding of what exactly is causing this processor exception and correct the script.
How to find the root cause of the processor exception
Below you can see an error example which is used to explain how you can find the exception root cause using Error stack trace.
Error Detail Message:
If you search in the error for CreateIssue, you'll find occurrences which would mean that it's a problem with your Create Processor script.
If you search in the error for ChangeIssue, you'll find occurrences which would mean that it's a problem with your Change Processor script.
If you can't find CreateIssue or ChangeIssue in the error, this means that it's a problem with your Data Filter script.
If you look up .groovy: , you'll find one occurrence like .groovy:8 , where 8 is the number of the line you have a problem with.
Basically a NullPointerException with a message "Cannot get property 'value' on null object" means, that on the line "43" of your Create Processor you are doing something like
For example, you're getting a value property:
Which means that you rely on the remote side sending some custom field, while it is not.
You should think of how would you like to handle situations when remote side is not sending a custom field.
Typically, we recommend using a null-safe access to handle absent values. Check the example below.
Find more details about the ?. operator here: https://tedvinke.wordpress.com/2015/09/25/avoid-nullpointerexception-safe-navigation-with-groovy/
To fix the error update appropriate script processor and retry synchronization once again.
Need support? Submit a request