Hi all! 
I wanted to see if anyone knew if the following automation was possible. My team is working in sprints and we want to bring the sub-tasks of an Epic (parent task) into the Sprint backlog only then are ready to be worked on. While I know we can manually multi-home the sub task to the current project, I was hoping to set up an automation that would run this when we changed the status to âReady to be worked onâ. However, when I tried, it looks like I can multi-home the sub task to a different project, but not the one that itâs currently in. (I can also create a new sub task to have multi-homed, but I need it done with one already created. (Does anyone have an idea of how to make this work?
Thanks in advance!
Hi @Val_Ward1 I ran into a similar use case. What ended up working for us was using a rule that creates the subtask only when itâs ready to be worked on, and assigns it to the project at creation time.
That way, the subtask doesnât exist (or need to be multi-homed) until itâs actually âactivated.â
Best,
Jeremy
FYI @Val_Ward1 you can do this via a rule action in our Flowsana integration - unlike Asana, our âAdd task to projectâ rule action lets you select the current project.
Hi @Val_Ward1 , although I would recommend @Jeremy_Longâs solution (and definitely worth checking out Flowsana.net by @Phil_Seeman) for what itâs worth, I think the only way to achieve what you want natively in Asana is to use an âAdd/move to sectionâ action, which happens to also add the subtask to the project (that the section is within), I believe.
Just make sure your rule is set to trigger on subtasks too.
Hi @Jeremy_Long, @Phil_Seeman, and @Richard_Sather thanks so much for your input here. I will look in to these different options! Appreciate your help!