Create a story including subtasks in another backlog when a story is done using automation.

[Maarten Verreck]

I have created an automation in backlo A that creates a story in backlog B when a story in backlog A is set to done. 
The story is created and all the fields and smart values are created in backlog B.

But...

I red that it's not possible to create a set of subtasks for that story in this automation.

So I'm trying to create this in backlog B. 

I already have an automation in place for creating subtasks when we create a story manualy in backlog B.

Somehow the trigger based on create story doesn't work when automation does this from another backlog. 

What trigger should I use for this action?

[Valerie Knapp · Accepted solution]

Hi @Maarten Verreck , thanks for your post.

Please can you share some screens of these automations with us? It is hard to offer advice without actually seeing what you are trying to do / how you are trying to do it.

It sounds like maybe the issue is this - that you haven't enabled the second automation to be called by the first

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180 

but it is hard to tell without seeing your rules.

Please provide more information so we can help.

Best wishes

[Maarten Verreck]

In backlog A I have build an automation to create a story in backlog B

In backlog B I created an automation that should create a subtask when a story has a creator that equals Automation for Jira. 
Somehow a story that is created by automation is not seen as a created workitem.

I use the automation below in most of my backlogs to add subtasks when I create a story or bug. This rule workes perfect.

[Maarten Verreck]

@Valerie Knapp Your suggestion works. I checked the option to be triggered by another automation and now the subtask is added. 
I also got an error, but that one I can solve. THX

[Taliah15]

Use the "Issue created" trigger in backlog B for the subtask-creation automation. Ensure filtering or conditions are set if needed, as this trigger does fire for issues created by other automations as well, not only manual ones. @Maarten Verreck  If this helps kindly let me know.