Can the Issue ID and Parent ID fields produced during CSV export be used to pre-define hierarchy

[Amy Sacchetti]

Can the Issue ID and Parent ID fields produced during CSV export be used to pre-define hierarchy linkages on new items added to the CSV so that I don't need to do it after import? 

So what I am imagining for all the new issues I'm creating in the CSV for Import, is putting self-defined IDs into those fields that are high enough numbers to not have been used already in the Jira environment and have those new IDs align to one another (Parent-Child) the same way the exported issues did for the old issues. 

If I can do this, would this cause issues when the natural issue creation in the tool reaches the IDs I created?

Additionally if I can do this, how many characters can those ID fields hold?

Thanks

[Amy Sacchetti]

Was able to test and found that I can do it, and it works, but am still curious if the IDs will run into issues later on.

[KAGITHALA BABU ANVESH]

Hi @Amy Sacchetti ,

Good Day …!

Issue id's are generated in Database level. auto incremental.

My suggestion is not to include issue id's in csv support. this may cause the production down, and these kind of things not cover Atlassian support policy.

Please refer these documents for csv import in jira.

for Cloud -https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ 

for Server - https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html 

Thanks,