How to enforce subtasks using Parent ticket transition workflow upon creation

[Katherine Chan]

We have different ticket types using different Status transition workflows.  When I create a subtask under ticket type A manually through the Create Subtask button, the subtasks are using the same workflow (workflow A) as the parent ticket as expected.  However, when I create a subtask using automation, it is using the default transition workflow for subtask ticket type (workflow B).  How can we enforce the subtasks created in the automation to use the transition workflow (workflow A) as the parent ticket?

[Katherine Chan]

It's resolved!  I found out some of the fields could not find the issue to copy from and there were errors (I used Parent Issue instead of Current Issue initially) and even when the subtasks were created, there was error and the status transition was not using the one from Parent ticket.  When I used Current Issue to copy the fields in the Create Issue rule, it worked as expected.