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,459,905
Community Members
 
Community Events
176
Community Groups

Cloud Migration Error: project-export Approval with MRI - mri:mig:jira/classic:issueStatus:10009 has

Hi everyone,

I'm trying to export a Service Desk Project to cloud and there's only one error in the log files:

 

2021-11-16 19:05:01.510 ERROR XYZ project-export Approval with MRI - mri:mig:jira/classic:issueStatus:10009 has missing Issue status with id - 10009. Verify if Issue status with id 10009 is valid.

 

I did find this Status and can confirm it's part of an approval process - but not in this specific project workflows used. So why should it be a problem?

Did anybody have seen this error before? What could cause this? And of course what can I do?

Thanks a lot!

Hannes

1 answer

0 votes
Andy Heinzer Atlassian Team Nov 24, 2021

Hi Hannes,

I see that you created a support case for this problem already.  For the sake of other users that might encounter this problem, we are tracking a bug relating to this error message over in https://jira.atlassian.com/browse/MIG-896

While that bug ticket currently has a workaround to enable a dark feature in Jira Server as a means to get past this, I see that you also found a means to work past this problem by adding that status back to the workflow in question before then migrating it again.

Regards,

Andy

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Atlassian Community Events