So we have a mail handler that pulls emails from exchange and creates tickets in JIRA, first step on the Create - Post Function it hits a .groovy script.
The groovy script will assign ticket priority, and then run the Summary (pulled from the title of the email) through some regex to pull info to be put to customfields, and set assignee.
At the moment atlassian-jira.log is saying it's erroring at issue.summary.toString()
In most scripting and templating languages, such as groovy or Velocity, these are going to do the same thing. These languages aim to make your life easier by examining the classes for methods that have names like
x.getFoo() and presenting them as if they were publicly accessible members
x.foo. This is just syntactic sugar and has exactly the same meaning.
If you are getting an error at
issue.summary.toString(), then my first wild guess would be that you're getting an NPE because
issue is unexpectedly
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs