Unable to migrate classic project to next-gen project due to bulk change restriction

[Prashant Patil]

Hi,

I am trying to migrate my old classic project to next-gen project on Jira cloud.

I tried to copy all issues to new next-gen projects, however, bulk change option allows me to copy upto 1000 issues at a time. I checked but there is no option to increase this limit in Jira cloud admin(maybe since I am using standard 10 user license) on Jira cloud. I believe there is option in Jira server but how to do it on cloud?Now if I try to migrate issues in batches of 1000, I cant do it as issues association is not allowing me to do the same. I am stuck here and cant find any other option. Please guide me on the same.

CSV export import option tried but not all fields (like status, priority) can be mapped.

[Prashant Patil]

As I mentioned, I face problem while migrating  issues due to their associated parents are not migrated in batch of 1000. Getting below error

Some issues will lose the relationship with their parent epic.

You're moving some issues away from their parent epic. To avoid losing the relationship between these issues and their parent, move the epic issue as well.

[John Funk]

What is your estimate of the percentage of issues that have a parent? I would move the those that do not have a parent (or child) attached first. And then if the number remaining is relatively low, then move them manually. 

Otherwise, move the parents first, the system will recognize there are children and bring them along. But don't start with children. 

[Prashant Patil]

Okay, as suggested I moved parents first and it allowed me to take all issues in batches.

Thank you for help. That solves my problem.

[John Funk]

Great - glad I could help!

[John Funk]

Hi Prashant,

Yes, you will only do 1,000 issues or less at one time. What error are you getting when you try to move fewer than 1,000?