You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
Default Custom Field Manager was deprecated a long time ago, and removed from version 7.
Try customFieldManager.getCustomFieldObjects(issue) instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.