How much complexity/risk does Scriptrunner add to Jira?

I had the chance to attend a Scriptrunner session as part of the Atlassian User Group meetings, and I learned quite a lot; I got a sens of what Scriptrunner can add to Jira, and how it can add complexity that affects maintenance and upgrades.  From what I gathered, depending on how far your scripts go, you can be digging deep into the undocumented guts of Jira, and Jira upgrades can render your scripts inoperable when those guts evolve.  

So my question is this - it's clear that there is a level of complexity and risk that Scriptrunner adds, but how much so?  

Bonus question: for admins who are not 100% dedicated to administration as part of their daily duties, does this level of complexity/risk increase exponentially?

3 comments

I think it's partially a function of the complexity of the scripts that you implement. With JIRA api changes, there is risk of scripts breaking (it's almost a certainty with a major JIRA release) and needing to be updated. I'm not a developer but I have been able to get by with Google-Fu.

You also have to make sure to test the plugin when you're planning a JIRA upgrade, as we just got bit by Scripted FIelds not working in ScriptRunner on JIRA 7.3.6 (they released a fix this morning).

ScriptRunner is much better than a lot of the plugins out there in terms of how much it keeps me up at night, but I'll bite my tongue and not name names... :)

There's a lot of large JIRA admin changes that are *much* faster when using ScriptRunner

I don't doubt that.  My concern is about maintaining the system and upgrading it.

Most of the features will upgrade with no work. If you have written scripts that use the JIRA Java API then that does change during major version upgrades. But that is true for Java add-ons as well. I haven't found that using ScriptRunner adds a large maintainence load.

Daniel Wester Community Champion Jun 21, 2017

It depends on what you're trying to do and how you use it.

If you limit your interaction with the shallow API and things that have been around for eons you'll be safer but if you start heading into the more experimental and newer code - the more fun you'll have. If at some point you end having built an addon using ScriptRunner(I've seen it done) - you'll probably want to build it as a real addon.

If you have a good testing/config mgmt approach it will help.

Scriptrunner is a really awesome and powerful tool but as they say with great power comes great responsibility.

Comment

Log in or Sign up to comment
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

199 views 1 3
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you