Migrate issues by keeping the same ticket numbers

[Arthur Harutyunyan]

Hi Admins,

I need your help on a very specific and, in my opinion, not realistic problem that I am facing. 

The situation is the following:

I have 2 Jira projects:

1) X - this is a team managed project with lot of tickets, around 5k. This project is actively used by the team within the last 5 years. 

2) Y - this is a new company managed project that we should migrate from X

So, the general task is to bring all the tickets from X to Y keeping all the relations, custom fields etc. 

Basically I solved the general task, using DeepClone app, thanks to the team for such a great tool. 

But, what is challenging here for me, that I was asked also to KEEP THE ISSUE KEYS THE SAME in the new project ;(. Meaning, that if there is a ticket in X-123, then if a clone this ticket to Y, then it should have Y-123 id in the new project. 

Any ideas how can I keep the IDs the same, because afaik Jira does not allow to do so. 

Thanks, 

Arthur 

[Luka Hummel - codefortynine]

Hi @Arthur Harutyunyan

Thank you for your praise and for also contacting our support.

I will add my answer also here, so others can find it if they encounter a similar problem.

It’s theoretically possible, but the source project needs to fit specific requirements. If you didn’t consider this when creating the project, it’s highly unlikely the issue IDs will match perfectly.

You can read how the clone process is ordered here. It’s currently not possible for us to specify issue keys when creating/cloning issues.

[Cédric Daemen]

Hello Arthur

if there are no tickets created in the new project, there shouldn't be any problems, but from what I understand this isn't the case.

So here's an alternative solution:

I created a custom field beforehand

In the team managed project:

in the company managed project :

I hope this might helps you, otherwise let me know,

Regards,

Cédric