Bulk-cloning of Jira issues
Asked by anuta_lucky:

Hi!

How can a user clone a bulk of issues in a project at a time?


Answers:
author: anuta_lucky
body: Thank you for your answer!


author: Nishanth Thimmareddy _Appfire_
body: Hi [@anuta_lucky](/t5/user/viewprofilepage/user-id/4514683)

Welcome to the community!

You can use [Clone Plus for Jira](https://marketplace.atlassian.com/apps/44043/clone-plus-for-jira?tab=overview) to bulk clone a number of issues from a project or different projects to the same or different project. This is available for Cloud and DC hosting options. Full disclosure: I'm the product manager for the app.

If you have questions or feedback about Clone Plus for Jira, please [get in touch with us](https://bobswift.atlassian.net/servicedesk/customer/portal/1) directly.

Regards,

Nishanth T

comments: author: Lisa Grau
body: There is no native Jira function to bulk clone issues. Only to bulk edit, move, transition, delete and watch, but you can use Jira automation to clone issues, if it fits your use case!


author: irene_angreini
body: Hi Lisa, can we use the bulk clone to clone the subtask inside the issue as well ? thanks!


author: Chitra Raj
body: [@Lisa Grau](/t5/user/viewprofilepage/user-id/5111668) Could you please guide me on how to achieve it through automation?


author: Jennifer Meronek
body: [@Nishanth Thimmareddy _Appfire_](/t5/user/viewprofilepage/user-id/2386318) I downloaded this and it did not work. I received a bunch of errors and no issues found.


author: Elena Kolesnik _Appfire_
body: Hi [Jennifer Meronek](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5233606), I am a Product Manager for Clone Plus. It is a pity to hear you faced some issues while using our app. Would you be able to raise a [ticket](https://appfire.atlassian.net/servicedesk/customer/portal/11/group/36/create/163) so that we can jump on a quick call to eliminate those? Thanks


author: Sarah Lynch
body: Can I clone the same task once but have 30 copies? I have a issue that is done daily but could be assigned to different persons, depending on the day of the week.


author: Nanagiri, Prashanth
body: I'm also looking for a solution on same use case. Did you find any solution?


author: Sarah Lynch
body: No unfortunately not.


author: Mechee
body: A little late but could be helpful, nevertheless: You can always export then reimport after removing the Issue key and any other Jira assigned values from the import file (i.e, keeping the fields you added --- summary, description, etc)

comments: author: Jo?o Monteiro
body: In my opinion, this is the quickest option and it is extremely versatile.


author: Kalpana Kukreja
body: In this case where you export and reimport issues into another sprint, is there a way that you can link the original exported issue to the one that is being imported to other sprint. I have a requirement where I need to reimplement same feature to another app configuration and I need to lookout for what changes were made during the original implementation. So I need the the link of original issue to the one that is being imported in new sprint.

Is there a way to do that?


author: Mechee
body: Yes. In your import file, make sure to include the sprint id of the new sprint (\*ID only--- not the name of the sprint) and a linked issues column.

Then when importing the file, set the configuration to have the original issue key map to the linked issue field for the new issues, making sure to set the link type to whatever you want the relationship to be.

![Screenshot 2023-06-20 160526.png](https://community.atlassian.com/t5/image/serverpage/image-id/264171iBC5771BE09DDF3EE/image-dimensions/296x203?v=v2 "Screenshot 2023-06-20 160526.png")


author: Gauthier ?stervall
body: \> sprint id of the new sprint

How do you get ahold of that?

EDIT: got it, through the [advanced search](https://ja.confluence.atlassian.com/jirakb/jira-software-how-to-identify-the-id-of-a-sprint-779159065.html).

Warning for other users: you need to export to csv, because import requires csv. I just did a load of search and replace and regexp and all that on an xml file... which cannot be imported. Yey.


author: Anna Tran
body: In my case I just added a loopback transition into my workflow and added a post-function that clones issues. That way you can bulk transition your issues and your issues will be cloned.


author: Marlene Kegel - codefortynine
body: Hi,

I am Marlene from codefortynine.

Another option to bulk clone issues would be our Jira cloud app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652/deep-clone-for-jira?hosting=cloud&tab=overview&source=community169).

You can start right away after you've installed our app from the Atlassian Marketplace:

* Filter for the issues you want to bulk clone using the Jira issue search
* Click on the Deep Clone button on the top right
* Select the target project and configure you clone
* Clone

![deep-clone-jira_bulk-clone.png](https://community.atlassian.com/t5/image/serverpage/image-id/224582iFB936755366A5C93/image-size/large?v=v2&px=999 "deep-clone-jira_bulk-clone.png")

For more details you can [read through our documentation](https://c49.link/deep-clone-for-jira/docs/bulk-clone), or watch our [demo video](https://c49.link/deep-clone/video/bulk-clone).

comments: author: Jeremy D
body: This was the one I was going to suggest.


author: Marlene Kegel - codefortynine
body: [@Sarah Lynch](/t5/user/viewprofilepage/user-id/5266644), welcome to the Atlassian Community!

With [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652/deep-clone-for-jira?hosting=cloud&tab=overview&source=community169) you can clone single issues, a bulk of issues and Epics multiple times. Simply select "Clone issue multiple times" in the Clone Dialog.

![deep-clone-jira_clone-issues-multiple-times.png](https://community.atlassian.com/t5/image/serverpage/image-id/276831iEC97E8C008A056F5/image-size/large?v=v2&px=999 "deep-clone-jira_clone-issues-multiple-times.png")


Tags: atl-gruland