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 me a stronger user of the tools.

Some of the information in this series will be relevant to both Jira and Confluence. Some of it will be specific to one platform or the other.  What I’m going to strive to do is provide examples for Cloud and for Server/DC. They’ll be separate blog posts, but hopefully posted at the same time, or at least close together.

ScriptRunner isn’t cheap, but it’s an amazing tool that extends Jira and Confluence pretty much as far as your imagination will allow you to envision.   There are trial licenses available for Jira and Confluence on both Server/DC and Cloud. 

Finally, if you have a topic or a question that you’d like me to cover as part of this series, please leave a comment or send me a message on LinkedIn!