Possibility of Keeping Issue Keys the Same When Cloning to a New Project?

[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

[Trudy Claspill]

I have just recently learned that using a CSV import you can force the setting of the numeric portion of issue keys, as per experimentation done by the original poster of this post.

But I concur with the other answers that you can't force the setting of issue key numbers when you use Move or Clone.

[Mikael Sandberg]

It is not possible, Jira will pick the next available number and there is no way of controlling that. Instead of cloning the issues what you could do is move them to the new project, that way Jira will forward users to the new project if they have a link to the old one.

For example, in my old project I have JRA-123 which I move to a new project (JIR) and in there the issue gets assigned JIR-111. I could then use either one of these to get to the issue.

[Samuel Gatica _ServiceRocket_]

Hi @Theresa Gothard 

I don't think that's feasible, since you are on the Cloud version, I suggest you contact Atlassian support and check with them if they can do some hack at the DB level.

Best regards

Sam