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

[Leos Junek · Accepted solution]

Finaly I asked Atlassian Support for help. Atlassian engineer found it is a JIRA bug and raised bug report  JRA-43401.

[Felipe Kraemer]

Hi Leoš,

I believe there should be a communication problem between the instances, because this should be working.

Can you please check if the Application Link is correctly configured? Are you able to see builds in a JIRA issue's Development panel?

Kind regards,
Felipe Kraemer

[Leos Junek]

Hello Felipe, thanks for your answer. Yes, Bamboo is properly listed in Application Links. I do not know anything about Development panel, but Bamboo builds are shown when listing single issues (card Build in issue view). Finaly your colleague found it is a bug - see my answer. With regards and thanks Leoš