nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I want to migrate project and generate the issue key like in an old project.

Mariam Hovhannisyan

In my old project (old project key SJT) I have some deleted issues and there was issue key sequence like this: SJT-1, SJT-2, SJT-4, SJT-5, SJT-7.

I want to migrate project and in a new project (new project key KLM) when I will import issues, issue keys have the following sequence: KLM-1, KLM-2, KLM-4, KLM-5, KLM-7.

Can I do it or issue key is not possible "adaptation"?

Accepted answers

Sagar Mahajan_d8sqh7

Hi @Mariam Hovhannisyan Yes, It is possible.

If you are importing the issue to new project and those issue-key's are available like KLM-1, KLM-2 issues does not exists currently then you can mention the issue-key numbers in the CSV file from which you are importing the issue,

If issue-key is already used then CSV import will update the existing issue matching the one from sheet. .

This way issues imported are created with the mentioned issue-keys, Please find the below screenshots for more information.

In another scenario if issue-key KLM-1,2,3,4 are already used and you want the new issues imported from CSV should have these issue-key and you don't want to loss the existing issues as well, Then you can move all the existing issue to any test project and then import the issues from CSV file (mention issue-key) and once all issues are imported then again you can move your old issues from test project to current project, these issues will use the next available issue-key for the project.

Let me know in case of any issues or questions.

Capture 2021-10-01 at 10.27.28.png

Capture 2021-10-01 at 10.23.52.png

Capture 2021-10-01 at 10.28.27.png

Capture 2021-10-01 at 10.29.51.png Capture 2021-10-01 at 10.29.29.png

All comments

Pramodh M

Hi @Mariam Hovhannisyan

Its not feasible as it is generated by Jira when you are importing new projects.

Similar Issue here

https://community.atlassian.com/t5/Jira-questions/Import-How-do-I-map-Issue-Key-Status-and-Resolution-in-CSV-to/qaq-p/58147

Thanks,
Pramodh

Sagar Mahajan_d8sqh7

Hi @Mariam Hovhannisyan Yes, It is possible.

If issue-key is already used then CSV import will update the existing issue matching the one from sheet. .

This way issues imported are created with the mentioned issue-keys, Please find the below screenshots for more information.

Let me know in case of any issues or questions.

Capture 2021-10-01 at 10.27.28.png

Capture 2021-10-01 at 10.23.52.png

Capture 2021-10-01 at 10.28.27.png

Capture 2021-10-01 at 10.29.51.png Capture 2021-10-01 at 10.29.29.png

Nic Brough -Adaptavist-

You can do this with an import, but you need to think about the numbering.

If you export SJT-1, SJT-2, SJT-4, SJT-5, SJT-7 to CSV and just import them without any amendments into KLM, then you'll end up with KLM-1, KLM-2, KLM-3, KLM-4 and KLM-5 because Jira simply imports them in order and creates new issues based on the project counter.

To retain the old numbers (but not project key, obviously), you can pad the CSV list with dummy entries which you can easily identify and remove later (give them a summary of "delete-me key is number" or something.

Your CSV should contain

SJT-1, SJT-2, SJT-3 (delete me), SJT-4, SJT-5, SJT-6 (delete me), SJT-7

Mariam Hovhannisyan

Thank you so much. I can do it!!!!!

Mariam Hovhannisyan

Thank you !!!!

Mariam Hovhannisyan

Thank you. Very useful information. I will try it ))))))

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud