I am entirely self-taught when it comes to ScriptRunner and Groovy. Everything I’ve learned has been through trial and error, and Googling different permutations of words until I find a solution.
A great deal of the information out there assumes that you already know how to work with ScriptRunner, Groovy, and Jira or Confluence. I found this to be terrifically frustrating when I first started, as I did not have the requisite knowledge to make use of the information that I was finding. I didn’t have the skills to put it into context, never mind making use of it in the specific use case to which I was trying to apply it.
For that reason, I’m going back to the beginning. I’m starting an ongoing series of blog posts about how to get started with ScriptRunner for both Jira and Confluence. You need to learn to walk before you can run, so for that reason I am calling this series the ScriptWalker series.
Not only will this hopefully be a resource for persons just starting out with ScriptRunner, but it will also force me to be sure that I can teach what I’m doing. In the end, that will make