What is the difference when you import the CSV file with issue key field mapping and without the issue key field mapping

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

   

Summary


When you imported the issues with issue key mapping you noticed that the system picked up the same sequence as what is in the CSV file instead of picking up the next issue key sequence in your project.

Environment

Jira Cloud.

Solution

When you are importing the CSV file and tick the box near the Issue Key field under the Mapping field value:

Importing the CSV file with the Issue Key field mapping:

When you import the CSV file, Jira will prioritise the issue key sequence in your CSV file on the already existing issue key sequence order.
Example: The last issue key was ABC-6356 in your project and in your CSV file you have XY-22222, when importing, Jira will drop the project key (in this case, XY) but will import the issue key (in this case, the 22222) so the new issue will be ABC-22222.

And if you create a new issue directly from the UI, the issue key will be ABC-22223.

Importing the CSV file without the Issue Key field mapping:

When importing the CSV file, but the Issue Key field is not selected, Jira will look for the last issue key sequence order and will add up to it.

Example: The last issue key was ABC-6356 in your project and in your CSV file you have XY-22222, but here the issue key field was not selected, after the import the new issue will have the following issue key sequence ABC-6357.

And if you create a new issue directly from the UI, the issue key will be ABC-6358.



Last modified on May 9, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.