Bulk Cloning Jira Issues, but need to keep same Issue Key

Theresa Gothard

Hello!  I'm maybe not going about this the correct way, so please let me know if there is a more efficient way to do this.  

We currently have a team-managed project that I'd like to move over to a company managed project.  I have set up the new project and would like to clone all the issues into the new project.  However, I need to keep the Issue keys the same (the letters can be different, but the numbers need to be the same).  In my research, I have not seen a solution to this, so maybe it's not possible?  

Or should I be going about this differently?

Thank you!

Theresa

Nic Brough -Adaptavist-

The only way to do this would be to create the issues in a strict order.

Imagine you've got 

• ABC-12
• ABC-16
• ABC-18 

That you want to clone and move into a project currently having the last issue as XYZ-10.  You will need to

• Create XYZ-11 (and delete it if you don't need it)
• Clone ABC-12 and move the issue into XYZ
• Create XYZ-13 (and delete it if you don't need it)
• Create XYZ-14 (and delete it if you don't need it)
• Create XYZ-15 (and delete it if you don't need it)
• Clone ABC-16 and move the issue into XYZ
• Create XYZ-17 (and delete it if you don't need it)
• Clone ABC-18 and move the issue into XYZ

This effectively makes the target project pretty much useless.

So, I have to ask - why are you wanting to do this?