In the current version of JIM importer, it is possible for us to specify the imported issue key. When importing the issues, the issue created will correctly be using the issue key specified in the CSV file, however this unfortunately will break the pcounter value in the project database. Hence as an outcome on this, the next issue created may be using the older value for issue key.

Sample steps to reproduce the problem:

• Create a CSV file:

  Issue Type, Issue Key, Summary, Description, Assignee, Reporter
  Bug,PCSV-14,Subject1, Description 1, admin, admin
  Bug,PCSV-31,Subject2, Description 2, admin, admin
  Bug, PCSV-45, Subject 3, Description 3, admin, admin
  Bug, PCSV-60, Subject 4, Description 4, admin, admin
  

• Import the CSV file to a new project
• The import will run successfully, and issues created will be using the issue key specified (eg: PCSV-14, PCSV-31, etc)
• However when we try to create a new issue, the issue key will be assigned to PCSV-5, which is incorrect. The expected next issue key should be PCSV-61. To check the pcounter value in database:

  select pname, pkey, pcounter from project where pname="project name";
  

Workaround:
update the pcounter value from the database:

update project set pcounter=x where pname="project name";

where x is a new value for pcounter