I want to build an automation that creates a task and subtasks

[Andrew Kwong]

HI, I've built an automation that clones an issue from one project to another and creates subtasks based on information from a portal request. In my initial version of the automation, I had static subtask names/descriptions such as "Men's Department cleanup!" and "See Action Plan Description" respectively. 

I'm trying to have my automation have dynamic subtask names/descriptions. I've linked the fields and thought that I made the relevant changes but I seem get an error message in the audit log that "Issues with this Issue Type must be created in the same project as the parent." I'm confused as this was not a problem when I had the static subtask names. Screenshot of one of my broken components and of the cloned case with static subtask names. 

[Trudy Claspill]

Hello @Andrew Kwong 

For the benefit of others, can you confirm that this relates to your previous post?

https://community.atlassian.com/t5/Jira-Work-Management-Questions/Automation-to-clone-an-issue-into-a-different-project-and-create/qaq-p/2415105

Can you show us all the steps in the Automation rule, including the Trigger step.

Also, please share the details of the Audit log for the execution that failed.

What is the project scope of this rule? You said you are cloning issues from one project to another. Is the scope for this rule set to Multiple Project and naming both the source and destination project?

[Andrew Kwong]

Yes, this relates to that post. I'm trying to build off of that. I've been trying a few fixes that seem to work, but only if 8/8 conditions are met. I then tested with certain conditions failing but the automation seems to break (issue cloned but zero subtasks created.) I tried reordering my components, but this doesn't seem to have fixed my issue. Screenshots attached of the top half of the automation; the bottom half is the same with more components. 

[Trudy Claspill]

Please show us the details of the Audit Log for an execution that did not give you the results you expected, and explain how the results diverged from your expectations.

[Andrew Kwong]

Hi Trudy, I've attached details of the audit log for the automation that did not give me the expected results. 

I've built a request form with multiple sections. Each of these sections essentially has a pass/fail question and two follow-up questions that generate fields that generate fields and a sub task in the cloned issue.

For my test, I've had the first question "pass" and the following questions "fail."

Actual Results: The issue is successfully cloned into a second project but zero sub tasks are created for the "fails"

Expected Results: Ideally, the issue should clone into the new project and there should be sub tasks in the cloned issue for each of the "fails." 

I'm stuck as to how to frame the automation to allow for both "passes" and "fails" without breaking every component after a "pass"

[Andrew Kwong]

Hi @Trudy Claspill , any ideas for this automation? Thanks!