I need to change the Issue Key

[Michael Pierotti]

My issue is I need to change the subtask key, or at least define how it assigns a Issue Key. I have created all my issues from a CSV import where I have used a customers project ID as the key so for instance FUZE Project ID 1724536 so I make my Issue Key VZW-1724536. Great, this works and it makes it easy for me to dump their database and import it into JIRA. Now, I then need to create a subtask to track specific site issues. I create a subtask and JIRA automatically assigns it as subtask VZW-1724537 as an example.... Well herein lies my issue. There is a VZW FUZE Project ID 1724537. So now I have a conflict.... When I import new issues that use the same Issue Key will it not overwrite everything I have on 1724537?

[Tommaso Gionfriddo _Adeptask_]

Hello @Michael Pierotti ,

For the reasons you have just encountered, it is a really bad idea to use issue keys for storing useful information.

Whilst it may technically be possible to work in the way you are asking about, it would require an incredible amount of complexity, which is absolutely not worth your time and effort.

Instead I would recommend creating a custom field which you can use to store the project ID, or even use the existing Summary field.

[Michael Pierotti]

Yeah, and there is still lies my problem. TO use the CSV importer, or pretty much ANY 3rd party tool from the marketplace it wants a KEY to import and there is no way I can manually create a key for 326 sites I am currently tracking every time I need to do a import...