Updating script runner from 2.1.17 to 3.0.16

I noticed the difference between our live JIRA server that has the 2.1.17 script runner with 49 modules enabled (vendor Jamie Echlin Ltd) and the script runner on our test server which is 3.0.16, has 88 modules and the vendor is Adaptavist.com Ltd.


My questions are:

  1. I guess that the modules are different because of the behaviors plugin is included in the new 3.0.16 also?
  2. If I'll update the 2.1.17 script runner - is the vendor and the modules amount will be updated and stay compatible with all scripted fields that were made with the older version?

Thank you in advance!

2 answers

1 accepted

This widget could not be displayed.

As Nic said. In this case the difference in numbers of modules is partly due to behaviours, but mostly because JQL functions are now their own modules so they can be individually disabled.

The script fields should be fine... but see Nic's more complete answer.

This widget could not be displayed.

New modules generally mean new functionality (or sometimes, a re-organisation of the internals).  In this case, some will be the Behaviours add-on being merged in, but others are new functions, and some may be down to re-organisation (I've not looked at the code, so I can't confirm that). 

The number of modules doesn't really matter that much to most users though, the only time an admin is that interested in the detail is if you want to turn one off to stop people using it.

There is no way to say that your scripted fields will be compatible (it's the other way around by the way - Script Runner is not compatible with your scripts, your scripts need to be compatible with Script Runner).  It depends on what they do and how - if they use functions in SR that have not changed in their implementation, then yes, your scripts are compatible and will continue to work fine.  If they use functions that have changed, then they may function differently or even stop working.  If that happens, you'll need to rewrite them.

Most people have relatively simple and stable needs from the Script Runner, and don't experience many problems upgrading.  But you need to examine and probably test every script, scripted field and behaviour does what you want in a test system before upgrading (I say "probably test" because when I'm upgrading, I can read some scripts and know that they'll work through experience.  If you have any doubt, you definitely should test them).  The common one at the moment is scripts stop working on upgrade because of changes in the way JIRA handles users when moving from 6 to 7 (not Script Runner, but JIRA!)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 17, 2018 in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

595 views 7 6
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