Looking to create sub-task during JSON import

[Robin Graysmark]

I am looking to create sub-tasks as part of a JSON import from an external system.

Our current tool creates the JSON data to import the initial issues (bugs ,stories).

I was look to either:

- Extend the conversion tool to create sub-tasks BEFORE we know the master issue

(Is this possible? If so, do we need to include "link" definitions in the JSON) or

- Develop another tool that uses REST api to map the Jira issues keys to the external system ids (customfield we have) and create another JSON file

I haven't quite figured out the correct JSON incantation to get a sub-task created.

Any help, guidance appreciated?

Thanks.

[Robin Graysmark]

An update on my request.

I was able use "links": and make use of externalId, sourceId, destinationId to create links between my issues (a "Bug" and two different custom "sub-task"s).

And they show up accordingly in the 'Issue Links' section.

However, I wanted them to show up as "Sub-tasks" as they do when a user manually creates the same sub-tasks. Is this possible?

NOTE: We are also using the Issue Matrix to group and name these subtasks.