So I have this automation that used to work in 2025 for cloning a task everyday with its subtasks attached to it. For some reason, the automation stopped working when it comes to the subtasks. The automation creates the task based on the template, but when it clones the subtasks, the parent issue becomes the template, and not the cloned ticket. Rovo told me to set the Parent issue as the variable i created but its not working and the automation isn't even cloning the tasks now. Any tips on how to solve this issue?
I’ve run into similar issues with Jira automation when cloning parent issues and their subtasks. One thing I’d check first is the order of the automation actions.
If the parent issue is cloned first, make sure the cloned issue is stored in a variable or referenced from the “created issue” context before attempting to clone the subtasks. The subtask’s Parent field should point to the newly created issue, not the original template issue.
I’d also check whether the automation rule is still able to access the cloned issue’s key/ID after the recent Jira changes. Testing the parent clone action separately first can help identify whether the problem is with the variable or with the subtask cloning step itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.