You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I know the bulk change limit can be increased for JIRA Server, but is there a way to do it for JIRA Cloud?
I want to migrate cca 2700 tickets from one project to another and need to do it in one batch to not loose connections between epics and tasks/stories. I would then put the limit back to 1000.
Anyone knows how to do this? :)
Yes, there is a limit of 1000 as this documentation states:
As an Atlassian employee wrote in on this feature request (which you can vote for here):
"We are moving this to a feature request for our long term roadmap. Supporting movement of over 1000 issues at a time requires an architectural change. Your existing votes will carry over and help with prioritisation decisions. Please continue to track our progress using this ticket. "
One option in the Marketplace called Deep Clone might satisfy your needs: https://marketplace.atlassian.com/apps/1218652/deep-clone-for-jira?hosting=cloud&tab=reviews&source=community248
This is a review I found from a user that was able to get about 2k issues closed:
"I was able to clone a Jira Cloud project with ~15K issues so that I could test the implications of changing its workflow and issue scheme. It timed out a couple of times, so I resorted to cloning in smaller batches of about 2K issues."
I hope that helps!
Hello @Marta Woźniak-Semeniuk
Can you check this question? How can I copy *all* issues from one project to an... (atlassian.com) Looks like there is a solution for server but not for cloud :/ But the app mentioned in the comment will help you.