Scriptrunner - "unable to resolve class" when upgrading Jira to V7.3.6 and Scriptrunner to V5.0.11 Edited

After the upgrade detailed above, scripted fields fail with the "Unable to resolve class" error for the following:

 

import DefaultCustomFieldManager.getCustomFieldObjects(com.atlassian.jira.issue.Issue);

 

These fields are mission critical to us, has anyone come across this error and can suggest a solution?

 

Thanks,

Dikla 

2 answers

1 vote

Default Custom Field Manager was deprecated a long time ago, and removed from version 7.

Try customFieldManager.getCustomFieldObjects(issue) instead.

Thanks Nic, 

Issue resolved :-)

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published 7 hours ago in Hipchat

Moving from Hipchat to Stride? Here’s what you’ll love

Heya, Hipchat friends! We’re so happy you’re checking out   Stride. Whether you know it or not, you have been instrumental in making Stride come to life. Every feature, design, and functionality...

30 views 0 3
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