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.
java.lang.IllegalStateException: ComponentAccessor has not been initialised.
This is not expected to occur on a production system.
Developers that encounter this message within a unit test
should use n MockitoMocksInContainer rule to initialize mockito and ComponentAccessor.
For more detailed explanation read the documentation
for MockComponentWorker in the jira-tests artifact for more information
about what causes this error and how to address it.
at com.atlassian.jira.component.ComponentAccessor.getWorker(ComponentAccessor.java:673)
at com.atlassian.jira.component.ComponentAccessor.getComponent(ComponentAccessor.java:160)
at com.atlassian.jira.component.ComponentAccessor$getComponent.call(Unknown Source)
at unlicenseusers.changeToInactiveUsers(unlicenseusers.groovy:54)
at unlicenseusers.run(unlicenseusers.groovy:122)
@Nic Brough [Adaptavist]Any help..Still struck in the same problem
Are your JIRA test and production systems the same version and running on the same version of Java?
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.
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.
Then what are the differences between test and production? How are they running differently? Check the system info page for both and look for differences.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Testing(groovy script) was done in the scriptrunner tool..and was working good in that..But when it comes to deploying in the linux server, running as shell script..this creates the problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, what?
What bash script? What has that got to do with JIRA? Why aren't you running the scrip in the same way you did on test?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bala,
Can you pls share the script for unlicensed users. Pls help me out. Thanks!
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.