Automation missing epic info for new issues?

[Noah Horton]

I have a rule that triggers on new issue creation. It sets a field in the new issue to that of the parent issue. Very simple one - all done through drop-downs and no custom JQL or such.

However, it does not work. When I create an issue using the "Create Child" in an epic, it triggers, but a condition checking that it has a Parent fails. Same thing if I change that to Epic instead of Parent.

My best guess is that the parent is not actually set through that create child method until after the automation has run. 

Anyone have any other ideas?

[Bill Sheboy]

Hi @Noah Horton -- Welcome to the Atlassian Community!

There is a known symptom where the Create Issue trigger can fire before all of the field data is available for use in the rule.

One work-around is to add a Re-fetch Action immediately after your trigger.  This will reload the data and slow the rule down a bit.

If that does not help, please post images of your rule and the audit log details showing what happens when the rule runs.  That may provide more context for the community to offer suggestions.  Thanks!

Kind regards,
Bill