Copy account from Story to sub-task after Story auto creation

[Matt Heidsick]

We have a project specific automation setup to create a set of sub-tasks once a Story is created,  

Another global automation checks if the account field is empty and if true copies it from the parent issue. 

It appears that these automations clash somehow, and the sub-tasks get created fine but they don't have an account populated. If I manually create the sub-task, however, the global automation works.

Anyone have experienced this before and how can I fix that ? Maybe a delay in the global automation rule if that's possible ? 

[Bill Sheboy · Accepted solution]

Hi @Matt Heidsick -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

By default, the actions of one rule cannot trigger another rule.  This to prevent errors and run-away rule looping.

When you intentionally want the actions of one rule to trigger another, try enabling the "Allow Rule Trigger" option in the details at the top of the rule for the downstream rule only.  Then test thoroughly and monitor your logs to look for any side-effects.

Kind regards,
Bill

[Matt Heidsick]

When you intentionally want the actions of one rule to trigger another, try enabling the "Allow Rule Trigger" option in the details at the top of the rule for the downstream rule only.  Then test thoroughly and monitor your logs to look for any side-effects.

That actually took care of the issue !!! Thank you !