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

[Soma King]

I'm downright ANGRY about this. I run into this several times a day, and this bug has been in Jira for years. It's 2018 now and I still encounter this. It impacts my productivity, and right now I can't upload anything even after quitting the browser and coming back in.

There's no shortage of 4 letter words coming out of my mouth.

Why are we paying maintenance when basic bugs like this don't get fixed?

[Abhishek Menon]

Hi I am also same issue on Jira v6.2.1,

Browser in question: Chrome: 33.0.1750

Firefox v29 works fine.

[Kris Decreton]

I am having the exact opposite problem with JIRA 6.2. Adding attachments in Chrome 33.0.1750.154 fails while this works fine in Firefox 27.0.1

[Kevin Maughan]

I am also getting this error, and with previous versions of Firefox. Maybe linked to getting a similar error when trying to move issues between projects? Neither issues are there when using Google Chrome.