Automation on Sb tasks

[Swaroop Kumar]

Hi Team, 

I've set up an automation rule to create 4 sub-tasks each time a task is created in my project. I'd like to setup another automation which would automatically change the status of these sub-tasks depending on the 1 first sub-task

for example, the status of the first sub-task (A) will be manually changed to ‘Ready to Test’. Based on this the status of the second sub-task (B) should be automatically changed to "Open".

Is this possible?

[Sanjog Sigdel]

I'm not there yet. So Far one of my automation creates a set of sub-tasks whenever a new story is created. Than my second automation assigns the sub-tasks to the one who transitions the ticket from To Do to In Progress.

Now anytime someone creates a ticket it will be assigned to them and creates a set of sub-task. Then the second automation assigns all of the sub-tasks to the one who changes the status of the ticket.

@Swaroop Kumar  Regarding your requirement though, why do you want to automate the flow of sub-task like mentioned above in the description? Isn't is team member's thing to move a subtask from ToDo to In Progress or to Open from the original state? If you implement above automation will it ensure that the developer/qa will have that ticket started?
Because team members pick tickets based on the priority and when they finish one task they are currently working on.

Can you share the use case for having this automation implemented in a team? From my point of view the first task if dependent will enable another tickets to be opened and worked on. But a story has say, test case preparation task, review, code development, code review and different sub tasks, which can run in in their own sequence.