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

JIRA Migration from Server to cloud failed due to - Status "Open" repeated in status assignments.


Hello all,

I  try to migrate a project from a JIRA server to a clound instance.


But I get an error (onyl 29 % is migrated)

Here is the first line of the error log file.


2021-04-20 09:35:51.913 ERROR NMP2 project-import We couldn't import Board 'NMP board'. Reason: Status "Offen" in Statuszuordnungen wiederholt. This caused 7269 other items to fail.


the german phrase :


Status "Offen" in Statuszuordnungen wiederholt



Status "Open" repeated in status assignments.


I think this is the root cause.


Any help and idea is more than welcome

Thanks  in advance




I checked  the workflow and the issue and seems to be fine.

1 answer

1 accepted

0 votes
Answer accepted
Phill Fox Community Leader Apr 20, 2021

@Reinhold Jaekle 

You say you checked the workflow but the actual error reported here is not specifically tied to the workflow but the configuration of the 'NMP Board'. 

I suspect that what you have are multiple references in the column configuration to statuses described as "Open" probably for different issuetypes.

This would be my next place to check. 


Also are you aware that you can raise a support request with Atlassian to help resolve issues like this if you are on a current licenced instance?

Go to and select the option for migration support. 

I hope these help you resolve the issue you are facing. 



Hello @JosephGill 

many thanks for your quick and valuable answer.

I will check the column configuration first . Might be this fixes my problem. very good catch. Thanks.


Also thaks for the link to the support web-site.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events