Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Scriptrunner Code Compatibility to newer Jira Software version

Christos Moysiadis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 24, 2018

Hello fellow Atlassians & Scriptrunners,

my little "problem" is to guarantee that the already written scripts (not by me , so i don't know the date&version are written ) are compatible to the new version.

Little info (current bild):

  • Jira Software version : 7.3.5 & Jira Service Desk 3.4.2
  • Adaptavist ScriptRunner 5.1.6
  • The plan is to upgrade every part to newest available version!

So....

  1. I've checked for major changes to the Scriptrunner Release notes already for deprecated methods but i didn't notice something special.
  2. Also i have copy/paste the scripts to Script Console to check if there is an auto-correction about failure or deprecated code, but all seems good.

Is anything else that i should do or an automated way?

PS.... the only process that i didn't made but it's planned ,is to run the whole script process logic manually and check if a problem is raised (they are not many scripts hopefully :P )!

 

Thanks in advance,

CM

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 26, 2018

I think you've done almost everything you reasonably can.  Your two steps on reading the notes and checking the auto-correct are pretty much right.

In an ideal world, your idea about the third step is exactly what you should do.  Get a test system and run through every script to check it does what you expect.

Personally, I've a nasty habit of skipping steps 1 and 2 when I'm doing a mid-level release and just running step 3 - if I start running into a lot of errors, then I go back and do 1 and 2. 

When I say "mid-level release", I mean if I'm doing an upgrade like 7.3.x to 7.7.x - the major version is not changing, so it's actually unlikely that scripts will start to fail, as Atlassian rarely change the APIs radically enough to cause a failure.  6.x to 7.anything is NOT funny - they deprecate a lot of code and change the way users work, so you really have to go over everything, but it is very rare that they remove something in a minor release.  So, in general , if a script is ok on 7.0, you can bet on it still working in 7.12 (maybe some deprecation warnings, but I would not expect it to stop working completely unless it's doing something daft like direct SQL access or trying to draw in unsupported libraries)

Christos Moysiadis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 26, 2018

Thank you a lot, again, for your advices and experience that you shared @Nic Brough -Adaptavist-

0 votes
Christos Moysiadis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 25, 2018

@Nic Brough -Adaptavist- I'm sorry that i mention you here without your permission but i didn't know another way to reach you! 

Is it possible to help me ? or do you know someone who had the same issue?

Suggest an answer

Log in or Sign up to answer