How to move 40k+ tickets between company-managed space in premium JSM cloud

Question

Hey team,

We have 2 company-managed project spaces in the same JSM cloud instance. We want to move all the work items (~40000), linked work items and associated attachments, comments, etc. with the work items. We want to preserve the "Reporter" and "Assignee" along with other relevant fields.

1. What is the best way to achieve this migration with native tools like "Bulk change"?

2. What are important considerations that we should address before executing the move?

Thank you,

Samar

Samar Tripathy · Answer

Thanks ArkadiusZ!

We have only option to use "bulk change". My intention is to move the work items, linked work items and associated attachments, comments, etc. We have active work items (<250) that are being worked. The rest of the work items are closed but needed for historical reporting. I am not planning to move all the closed work items at once but in chunks of 1000 or less. However, we want to keep the reporter, assignee, timestamps, comments, etc. like they are available at the moment. And this is the most important thing that we want to achieve.

Samar Tripathy · Answer

Thanks Ugnius!

My intention is to move the work items, linked work items and associated attachments, comments, etc. We have active work items (<250) that are being worked. The rest of the work items are closed but needed for historical reporting. I am not planning to move all the closed work items at once but in chunks of 1000 or less. However, we want to keep the reporter, assignee, timestamps, etc. like they are available at the moment. And, this is the most important thing that we want to achieve. We have only option to use "bulk change".

I am aware of the limitation regarding number of work items being moved. I am trying to figure out what are considerations before I move them.

Thank you!

Arkadiusz Wroblewski · Answer

Hello @Samar Tripathy

Your main options here are Bulk Move, the REST API, or using an app.

The important part is that Bulk Move and REST API approaches should usually be done in small batches, not all at once. You also need to make sure the configuration on both sides is very close, otherwise you can run into mapping problems during the move.

And if this is a Jira Service Management project, be especially careful. That is where things can get messy quite fast, for example when comments suddenly end up with the wrong visibility and become public when they should not.

Because of that, an app-based approach may be the safer path here.
Maybe Deep Clone for Jira would be worth a look.

You could use the trial, test the move, and cancel it afterwards if it is not needed anymore.

Deep Clone for Jira | Atlassian Marketplace