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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,552,363
Community Members
 
Community Events
184
Community Groups

Jira Server to Cloud Migration Error: IllegalStateException

Hi, 

 

I get this error when trying to migrate Jira server to Jira Work Management using the Jira Cloud Migration Assistant:

2022-11-02 16:13:00.242718 ERROR ARS project-import We couldn't import Project ARS. Reason: IllegalStateException: No message. This caused 512 other items to fail.

All my projects fail to migrate due to this error. This is after passing all pre-migration checks.

What could be causing this?

Regards

Brad

2 answers

1 accepted

0 votes
Answer accepted

The problem was eventually isolated by Atlassian support. When we upgraded from Jira 6.4.14 to Jira core 7.0.11 in the past, Jira automatically set all the "Project Types" for each existing project to "Software". This makes no sense as Jira Core doesn't provide access to the "Software" Project Type.

 

There is seemingly no documentation that speaks about this issue, nor is it mentioned as a problem within the migration documentation. Atlassian will look at adding this to their documentation in future.

 

Once the projects had been set to "Business" project type instead, the migration succeeded. [project name] -> Project Settings -> Details -> Project type(required)


https://confluence.atlassian.com/adminjiraserver/jira-applications-and-project-types-overview-938846805.html

1 vote
Benjamin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 02, 2022

HI @Bradley Rottcher ,

 

would recommend to check the jira logs to see more details of the issue. With additional details, can help identify which solution to apply. For example, if it's a version issue:

 

https://confluence.atlassian.com/cloudkb/we-couldn-t-import-project-version-because-of-missing-dependencies-project-jcma-error-1101926685.html

In certain cases, the DB needs to be updated.

 

Suggestion would be to see if the logs provide more details. If not, submit a ticket to Atlassian support to help troubleshoot the issue. In the mean time, see if you can deselect that project and migrate the rest of the projects over.

 

Thanks,

 

Ben

Hi @Benjamin,

 

Thanks for your assistance. All my projects fail to migrate due to this error, so I cannot deselect one project and migrate the rest of the projects over.

 

The jira logs do not show migration errors. I have looked extensively. Perhaps I am missing something. Can you perhaps let me know which jira logs on the server show migration errors?

 

With regards to the DB, can you let me know what exactly needs to be updated?

 

Kind regards

Brad

Benjamin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 03, 2022

HI @Bradley Rottcher ,

 

The log to check would the main log which is Atlassian-jira.log.

 

As for the DB, there is not enough info at the moment to know exactly what to change. Making any changes to the DB is a high risk without knowing the root cause. I would suggest to connect with Atlassian support. They can help with the migration issue you are facing. Just make sure to send the support.zip when you submit your ticket. the support.zip can be downloaded from the UI.

 

-Ben

Hi @Benjamin ,

 

I have thoroughly checked and I assure you the above errors received in the Jira cloud Migration Assistant do not appear in atlassian-jira.log.

 

I have logged a support request with Atlassian - still waiting for assistance.

 

Brad

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events