Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Cloud Migration

We used JIRA cloud migration to move ~60 projects to the cloud instance last week without issue. Now today we're trying to move a last and final project to finish our move and no matter what permission schema I apply we get this message after it attempts to migrate: 

 

2020-07-09 19:30:32.145 ERROR HA project-import We couldn't import Project HA. Reason: IllegalArgumentException: Permission scheme [10002] does not exist. This caused 121379 other items to fail.

 

 

4 answers

1 accepted

2 votes
Answer accepted

Given the information from @Jason Wong I was able to workaround this limitation. I created a new permissions schema by copying the default and then assigned my project to that schema. This allowed the tool to migrate the project successfully. 

2 votes
Jason Wong Atlassian Team Jul 09, 2020

Hi @Brennan Hitchcock

I think what's happened here is that Permission scheme [10002] had been previously migrated using Jira Cloud Migration Assistant, but then after that first migration run, it's likely that it was then deleted in Jira Cloud. Do you recall deleting it? Can you find it in the UI or is it now no longer there?

The Jira Cloud Migration Assistant has a mapping service that keeps memory of what has been migrated, and is programmed to relink to objects that have already been migrated in a previous run. This is so that we keep the configuration relationships the same and avoid migrating duplicates and causing a mess in Jira Cloud.

The details of how this mapping works are in the diagram on this page - https://confluence.atlassian.com/cloud/how-the-jira-cloud-migration-assistant-links-your-data-993925217.html 

 

A current limitation is that when something that has been migrated has been deleted, this mapping memory is not deleted accordingly. This is why when you run a migration involving that deleted item (in your case Permission Scheme [10002]) the Jira Cloud Migration Assistant then returns an error as it is expecting to link back to a previously migrated object that was deleted.

Do that seem to be the case?

We are investing ways to improve on this - so I'd encourage you to comment and vote on this ticket - https://jira.atlassian.com/browse/MIG-163

I will follow up by opening a support ticket for you - Our support engineers will be able to reset the memory for you manually and help you though this situation. We will be in touch shortly!

 

Jason Wong

Product Manager, Cloud MIgrations

@Brennan Hitchcock - please re-post your error message examples to your MOVE ticket (you should see an update in your email) and @Ting _Chiou Ting Teh_ will help you work through the issue.

@Jason Wong - Yes we did do a schema cleanup after the initial migration not realizing that the process wouldn't move the appropriate scheme with a subsequent project migration. I'll post this over in the MOVE ticket as well but I'd like any solution posted here as well for future people having the same issue. 

Like Jason Wong likes this

sorry, overlooked something

Hi, Brennan. Sorry for the late answer, but I felt the need to stop by and suggest an automated solution for everyone who’s browsing Atlassian with a similar issue.

Indeed, you can use the schema method, which is a proven but tedious option to migrate projects to Jira Cloud. Or, you can use our service and get the same results ten times faster with less headache. It’s called Help Desk Migration, and it’s an automated solution that will allow you to seamlessly transfer the needed data. In case of interest, you can find our service on the Atlassian Marketplace: https://marketplace.atlassian.com/vendors/1215318/help-desk-migration

By the way, you can test out our tool completely for free, and based on the trial results, make an informed decision. Feel free to check it out.

There was already an accepted answer here that can be accomplished without paying for / exposing your data to a third party. Please keep the shameless self-promotion out of long closed issues. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Cloud Migration

Cloud migration resources roundup: May 2021

...est practices.   And don’t forget about the tried and true! Cloud Migration Center - central hub for all things Atlassian Migration Program. Includes links to our full resources page, s...

134 views 2 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you