Normaly it should be sufficient to replace the script. If this doesn't work use the built in script "Clear classloader or jira internal caches" from the script runner plugin to reset the groovy classloader cache.
This is weird. I have classes which are used by listeners or scripts which are not refreshed if I copy a new file to the server, but they are always refreshed if I clear the groovy classloader cache. Maybe you should provide more details about your installation (script runner plugin version, JIRA version and environment) and hopefully @Jamie Echlin could help?
Henning - Thanks for sticking with me on this one! I've never had this problem testing scripted post functions, as those always reflect the latest version of the script. However, given my lack of experience with Groovy/Java, it's entirely possible I'm doing something very silly and just can't see it.
I'm testing my code using the SDK (version 4.2.9) on a windows 7 32-bit PC. I start JIRA with "atlas-run-standalone --product JIRA --version 6.0.1". I am using scriptrunner version 2.1.15. I figured that once I had it working, I'd move to my staging server and verify performance before going to the live server.
The listener itself doesn't really do anything at this point - all I'm doing right now is logging various custom fields.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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