Jython Script Runner is breaking since JIRA 7 Upgrade

It looks like the Jython Script Runner is breaking since the JIRA 7 upgrade as even on a blank script, it shoots back the following error message: 'com.atlassian.jira.ComponentManager' object has no attribute 'getJiraAuthenticationContext' - Any advice?

2 answers

This widget could not be displayed.

Hi Charles, have you found any solution for that?

After the upgrade I am getting the error:

<module> cfm = ComponentManager.getInstance().getCustomFieldManager() AttributeError: 'com.atlassian.jira.ComponentManager' object has no attribute 'getCustomFieldManager'

from scripts that were running fine on JIRA 6.2 sad

Hi, you should use ComponentAccessor instead, see https://docs.atlassian.com/jira/latest/com/atlassian/jira/component/ComponentAccessor.html

 

Btw i've finally solved ( hopefully ) my problems with jss after upgrading from JIRA 6.x to JIRA 7.x.

it seems in fact that upgrade functions are bugged and even disinstalling jss does not work ( maybe because of some kind of configuration left on JIRA database i guess ).

in my case that lead into having old content of 

/var/atlassian/application-data/jira/jss/jython

 

not updated, and also jython_2.5.2 deleted if i used "reinstall Everyting" from JSS installer menu.

to sum up, i had to 

  • uninstall jss plugin and install your new version.
  • check if  jython_2.5.2 was populated ( if not use a copy from your old installation )
  • check python files in 
    /var/atlassian/application-data/jira/jss/jython

    if they still import componentManager they are 6.x ones.

  • eventually remove all old content of jython folder and replace it with the content of jss_base_scripts.zip contained into jss jar file.

 

This widget could not be displayed.

Hey Marek,

As I recall, I had to completely remove the Jython Runner Plugin from JIRA (uninstall from admin AND go into the file system to remove the jython folders and files). It seemed like there were weird permission errors happening from the upgrade regarding that plugin.

Hope that helps,
Charles 

Hi,

Actually, I found out that ComponentManager.getCustomFieldManager() method was deprecated and ComponentAccessor.getCustomFieldManager() should be used instead of it.

I had to re-write my scripts a bit, but it finally works just fine smile

 

Sorry to bother you after few months wink

No worries, I like to see communication about this stuff! smile

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published yesterday in Marketplace Apps

The 7 hacks of highly successful automation

...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...

132 views 0 9
Read article

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