Automation on SubTasks Moving

[Scott_Hamilton]

Hello, I am looking for some assistance, without a plug-in on the following use-case.

1. When a Story is created that matches a given criteria, create 2 subtasks (COMPLETE)
2. When the story moves to In Progress, bring the Copy Subtask out of the Backlog (COMPLETE)
3. When the Copy Subtask moves to REVIEW, bring the Design subtask out of the Backlog.

I have the first 2 conditions working, but the 3rd one is the one that I am struggling with right now. 

I've gone through a couple of iterations, currently I have this logic setup

I'm having trouble identifying the other subtask and being able to transition it out of the Backlog. Thanks for any assistance!

[Scott_Hamilton · Accepted solution]

I actually was able to get it to work using the following.

1. When Issue transitioned from In Progress to Review
   1. Issue Type Equals Sub-task
   2. Asset Equals Copy
   3. And compare two values {{issue.dueDate}} = {{issue.dueDate}}
2. BRANCH
   1. For JQL type="sub-Task" AND  "assets" = Email
   2. Then Transition

[Bill Sheboy]

Hi @Scott_Hamilton 

How do you know an issue is the "Design subtask"?  For example, by some field value?

Once you have identified that criteria, you could either add that as condition inside of the branch on subtasks, or change to a branch on JQL to get that exact issue.

Kind regards,
Bill

[Scott_Hamilton]

Hi @Bill Sheboy,

In my original automation, when i create the subtasks I copy the original story name plus ": Design" or plus ":Copy". I copy some of the fields from the parent, while others I am custom setting based upon what the task is. This includes assigning a custom field Asset or either Copy or Email.

So I am trying to make it so when the subtask asset:copy moves to review, then the subtask asset:design moves oout of the backlog.

After the screenshot, my current branch is

• For: Sub-tasks
• Assets contains Email

Then transition it out of the backlog. But it doesn't appear to be finding the adjacent subtask