I have an automation running to clone a task from one project to another when status is changed. Can I also create a sub-task for the clone in the same process?
Hello @Md. Abrarul Huda
I believe that you can.
After the Clone Issue step add a Branch -for each Related issues / most recently created issue. That should shift the context to the issue created by the Clone action. Then you can add a Create Subtasks action inside that branch.
I can't seem to do it after cloning between 2 different projects. If I add a transition inside one project, it works perfectly. But after I have moved to a different project I got "Issues with this Issue Type must be created in the same project as the parent. (project)" error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please paste screen images showing the current state of your rule, and all the details from the Audit Log for execution of the rule.
Also on the Rule Details page what have you set as the Scope of your rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Attaching 2 screenshots. I guess the problem is visible. But how to solve it is the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I notice that while you said you are coming an issue, you are actually using the Crest issue action instead.
Please share the details of the step where you are creating the subtask.
Additionally what is the scope of the rule specified on the Rule Details page?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was initially cloning an issue. But then I tried the create new issue action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to implement the solution I detailed in my first response - use of a For Each branch after you create the new parent issue. The add the step to create the subtask as a subordinate step in that branch.
In your current implementation you are setting the parent of the subtask to Current Issue which, in this case, is a reference to the trigger issue rather than the issue you just created. You have to use a Branch to shift the focus to the newly created issue.
You may also need to change the scope of the rule to be multiple projects and list the project that contains the trigger issue and the project where you are creating new issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Md. Abrarul Huda
If you're seeking for an easier way to clone an issue on a status change with their sub-tasks, you can try our app Elements Copy & Sync that allows you to clone and sync issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.
You can check our guide here.
You can try the app for free during 30 days (and it stays free under 10 users).
Kind regards,
Clara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.