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?




2 answers

This widget could not be displayed.

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

Try customFieldManager.getCustomFieldObjects(issue) instead.

This widget could not be displayed.

Thanks Nic, 

Issue resolved :-)

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
Posted 5 hours ago in Europe

Topic Tuesday: How did you learn about the AUG programme?

Back in 2010 I hadn't been using the Atlassian tools (JIRA, Confluence, Bamboo) that long and I started searching online to see if I could chat to other users primarily about how they used the produc...

13 views 0 0
View post

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