Create a child ticket that copies parent fields automatically

[Michelle Rose]

I want to build this automation if it's possible -- 

I create a child ticket off of an initiative or epic for example (like in screenshot 1) and when I create it, certain fields from the parent automatically persist to that child ticket.

Right now my automation only works if I create the ticket through the generic creation menu / filling out the parent link field on that menu outright (screenshot 2). But that creates a lot of issues, it would be so much easier if the automation worked via scenario 1. 

[John Funk]

Hi Michelle,

What is not working for you in Scenario 1? 

And can you post a screenshot of your current Rule? 

[Michelle Rose]

@John Funk The fields don't cascade down. And I get this error from the automation (attached). 

I have to link the epic to the initiative in the create issue menu in order for the automation to work, but I want it to also work if I create the epic separately and link it to the initiative after.

[Bill Sheboy]

Hi @Michelle Rose 

Adding to John's answer:

That symptom can happen with the Issue Created trigger because it fires so quickly that some data for the issue may not be available at the time the rule starts...such as the parent key from which to copy the fields.

The work-around for this is to always add the Re-fetch Issue action immediately after the Issue Created trigger in your rule.  This will slow down the rule and re-load the data before proceeding.

Kind regards,
Bill