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.
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".
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:
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)😢
Let me share a document which I’d you to review:
Keep in mind that increasing the number can impact on the server performance.
I hope it works for you!
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.
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.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
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