Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Scriptrunner: Clones an issue, and links:Script function errors!

I am using "Clones an issue, and links" post function and I got this error after upgrading to JIRA 8 , anyone can help?

Script function errors!


  • The script could not be compiled:
    org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
    Script69.groovy: 2: unable to resolve class com.atlassian.jira.ComponentManager
     @ line 2, column 1.
       import com.atlassian.jira.ComponentManager;

2 answers

2 accepted

1 vote
Answer accepted

Well a lot of things have changed since jira 7 with the removal of ComponentManager. 


A quick fix could be to use 

import com.atlassian.jira.component.pico.ComponentManager

But that is in no way a long term solution.

0 votes
Answer accepted
Niranjan Rising Star Sep 17, 2020

Hi @Juhaina Almama ,

You should use import com.atlassian.jira.component.ComponentAccessor instead of the deprecated ComponentManager method.


thanks for answering

I used it but I get error:


Niranjan Rising Star Sep 17, 2020

These are not errors, but generally warnings indicating the deprecated methods. You may need to replace them with the ones compatible with the current version of your JIRA.


Use getCustomFieldObjectsByName(String) instead of getCustomFieldObjectByName

Like Juhaina Almama likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events