What is the best way to copy issues from one project to another

[Zaldy Parian]

Hi all,

We created another JSM project and we want to copy issues from the old project to the new. What is the best way to achieve this?

We want to keep the issues from old project and have the permission updated to read-only. I cannot use bulk move because it will remove the issues from old project.

Only crude way I could think of is to export the issues to a CSV or Excel file and then import the issues to the new project.

Any suggestions, please?

Regards,

[Brant Schroeder · Accepted solution]

@Zaldy Parian Your crude way would be the only way to do it without an app from the Atlassian marketplace. There are apps that allow you to clone the issues.  You could try them for free and see if they will work from you.

[Zaldy Parian]

Thanks @Brant Schroeder ,

I'll search for a free apps that will help me with this.

Regards,

[Brant Schroeder]

@Zaldy Parian You can use a paid app as well.  If you are using it for the first time it should have a 30 day free trial.  If you like it and you think you can use it to accomplish this more often you could always purchase it.

[Thibaut Subra _Elements_]

Hello @Zaldy Parian 

Indeed, if you want to try an app for free, we developed an app called Copy & Sync that will help you with that. Using our bulk copy, you can clone all your project issues as well as the hierarchy (from Epic to subtasks).

Let me know if you need more information, I'll be glad to help!

Regards

Thibaut

[Sanjog Sigdel]

@Zaldy Parian I would suggest you to move issues to new project using bulk operation.

1. In the issue navigator search for Project = "Your Project Name"
2. Now Perform Bulk Operation and move them to another JSM Project.

Bulk Operation works for both Jira Projects and Jira Service management projects.

Limitation and Work Around

Limitation :- The Limitation about jira query is that by default in the  we can list only 1000 issues.

Workaround :-  Perform bulk operation twice thrice or N times unless all of your tickets are migrated to new project. It is not much of a hard work. Its simple redundant activity which gets your job done.

[Zaldy Parian]

Hi @Sanjog Sigdel ,

Thanks for moving it will remove it from the source project. Our business requirement is to keep it in the source and migrate it to the target project.

But I guess, I'll try some free apps that can do this trick.

Regrads,

[Luka Hummel - codefortynine]

Hi @Zaldy Parian

You can try out our app Deep Clone for Jira. I think our Bulk Clone feature would be perfect for your use case.

The app is free to try for 30 days and if you have 10 or less Jira users on your instance you can continue to use the app for free 🙂

[Zaldy Parian]

Thanks, @Luka Hummel - codefortynine