How can I copy *all* issues from one project to another? Bulk edit has limit of 1000 items.

[Shane Kremer]

We're currently using a "teams based" project and there huge limitations. We need to move to a "company managed" project instead.

I'd like to first do a copy of all the issues, check to make sure everything works fine and then do a final migration.

However, the bulk edit feature only allows you to edit 1,000 items at a time. There is a warning that tells you that we will lose dependencies, links, parent/child relationships. I don't want to lose those relationships and it would be hugely troublesome to rebuild that.

I haven't been able to find an answer on how to move all 5000+ issues, their links, dependencies, attachments, assignees, etc. to a new company managed project.

Help!

[Marlene Kegel - codefortynine]

Hi @Shane Kremer,

I am Marlene from codefortynine.

Another option would be our Jira cloud app Deep Clone for Jira.

With our app you can bulk clone and move up to 100.000 issues at once.

There are several steps before and during cloning that give you feedback on whether all fields/issues can be cloned. This helps a lot to make sure that not data gets lost. 

You can read more about migrating issues with Deep Clone for Jira in our documentation.

In the attached screenshot you see the "Deep Clone Progress Dialog".

[JB]

I'm about to encounter the exact same issue but as you would probably expect, I am not a JIRA admin (I am coming from a Team Managed project after all !)... .so I have no access to modify that advanced setting!!!


I am planning to move my cards epic by epic (or groups of a bunch of epics at a times) with all attached child cards to maintain all the links .. in this way I think each batch will be less than 1,000. Then when I'm done, I'll go back and hopefully the cards that are leftover will be less than 1,000 in total also... (I hope from our relatively good board hygeine there are relatively few story cards without epics).

Be aware that if you think you've "exported" all your issues/cards as a backup.. you've probably only export 1,000 so far.. and need to do this dirty hack to make sure you have backed them ALL up:

https://confluence.atlassian.com/jirakb/increase-issue-limit-for-excel-exports-in-jira-cloud-779160811.html#:~:text=By%20default%20both%20JIRA%20issue,export%20the%20first%201000%20issues.

[Shane Kremer]

Thanks, JB.

I thought about this approach as well, but unfortunately, my epics have cross dependencies with each other as well. It's possible I could just remove those dependencies, make the move and put those back in. That would be much less work.

[JB]

Atlassian haven't really provided a way to make it "much less work" so good luck

.. as it also turns out that migrating from Team Managed to Company Managed, the "Epic Name" field won't "retain" and needs to be typed in (as it is a compulsory field in our configuration) for every single epic migration !! yep. so I had to do them all one by one (or else chose to lose all the parent/child linkages - either way I was forced to manually work with every individual epic)😢

[Shane Kremer]

It might be too late for you, but I was able to use the plugin "Deep Clone for Jira" to move from a team managed to company managed. It worked very well for me. Just make sure that your destination project has all the same statuses and issue types.

[JB]

it is too late for me, but not for others in my org .. I'll pass this on ! thanks for the tip.

[Rodrigo Bruch]

Hi Shane!

Let me share a document  which I’d you to review:

https://confluence.atlassian.com/jirakb/increase-the-number-of-issues-that-can-be-bulk-edited-in-jira-1072223961.html

Keep in mind that increasing the number can impact on the server performance.

I hope it works for you!

Best regards,

Rodrigo

[Shane Kremer]

Thanks for the quick reply @Rodrigo Bruch !

I'm in the advanced settings and I don't see a key for editing the bulk editing limit.

jira.bulk.edit.limit.issue.count   

 I don't see a way to add key value pairs on this page as well.

We have Jira Cloud, so I don't believe we have direct access to the jira config file.