Can we create epic and its linked user story through single json ?

[Vishal Sitpura]

I am using this json to create and epic and user story in one transaction. however, it giving me the exception.

{

    "fields": {

        "project": {

            "key": "AU"

        },

        "issuetype": {"name": "Epic"},

        "customfield_10011": "Epic 1",

        "summary": "Epic 1",

        "duedate": "2023-01-18T00:00:00",

        "reporter": {

            "accountId": "abc"

        },

        "priority": {

            "id": "3"

        }

    },

    "fields": {

        "project": {

            "key": "AU"

        },

        "issuetype": {"name": "Story"},

        "summary": "User Story 1",

        "duedate": "2023-01-18T00:00:00",

        "reporter": {

            "accountId": "abc"

        },

        "priority": {

            "id": "3"

        },

        "customfield_10014" : "Epic 1"  -- This field is for epic link

    }

}

[Bill Sheboy]

Hi @Vishal Sitpura -- Welcome to the Atlassian Community!

I suspect the answer is, "no".

The Story create would need the issue key from the created Epic, and the Epic has not been created at the time you submit the JSON.  And without knowing the internals of how Jira is processing the JSON we may not be able to assume this is iterating and processing those nodes in the order you show them.

Kind regards,
Bill

[Vishal Sitpura]

@Bill Sheboy Is there a way we can create issue key by our own and not auto generating from Jira ?

[Bill Sheboy]

Not that I am aware of: the key is generated when the issue is created.

[Craig Nodwell]

Hi @Vishal Sitpura welcome to the community.  What is the exception?