Hi! Is there any possibility to set dependencies for tasks created using rules?
Adding subtasks using rules is a great feature, I use it to create custom sets of tasks depending on a type of pipeline that we use for production, but dependencies there is what it really lack.
Here’ s use case why I need it and why using template does not really work for me.
I have a form for feature request whic allows me to gather feature detailed requirement and I am totally happy with it.
As we all know form creates a task. But to create a feature it takes more than 1 task, as you probably all know
I use combination of custom fieds and ruled to add specific sets of tasks - design, development, testing and other custom sets, directy under the initial request created from a form - and it works fine.
Inside those sets tasks should have dependencies, but I cannot set them when i set up rule for adding those sets.
So the question is - how can I do it whithout having to create a task container aside (cause I can set dependencies using templates but that means I should copy all requirements already listed in a request task to a new template every time and place the “requirement task” inside of my template created container not to loose initial request which is way more actions to do and time to spent if you have say 100 requests to convert to task containers …
Any ideas/advice?
Hi @Larysa_Vyshnia, while using templates is currently the only way to automatically set dependencies between tasks, hopefully introducing the option to do this with Rules is something our Product team can implement in the future.
I’ll keep you posted and let you know if we have any updates
I want to create a rule that assigns an approved once the task moves to the section (that bits easy). What I also want to do is set the task to be dependent on the sub-task approval just created, blocking the task.
While it’s not possible to set dependencies with Rules right now, hopefully it’s something our Product team can implement in the future
We do have an existing thread for this feature request in the #productfeedback category so I’ve gone ahead and merged your post with the existing one to consolidate feedback.
I’ll keep you posted and let you know if I have any updates
I would also appreciate such a feature. I try to set up an approval process for new IT resources. Technically you can do that in two different ways.
You can create sections for each approval step and let the task (“New IT-Resource”) via rules move automatically to the next section whenever the approval was done. While this works just fine from a technical standpoint there is also a big downside: each approval has to be done one after the other meaning that if two or more approvals are connected thematically, they aren’t notified at the same time and have to approve successively. The other way is to automatically create Approval subtasks to a main task. If you then set the main task as dependent on those sub tasks you can create a rule "Once dependencies are gone, update the main task to “Approved”. This would be great if there would be the possibility to set this dependency automatically. Without that possibility this way is no real option for me cause someone (maybe me) would have to do this manually every time, a new IT Resource main task was created.
It would provide an increased level of clarity and efficiency if we could automate dependencies for subtasks that are created using workflow and rules for a project.
I’m somewhat new and couldn’t find an answer here.
Using the workflows I’m creating a submission form that triggers subtasks which have natural dependencies, is there a way to automate those dependencies instead of having to manually go into the task? If it isn’t built into the product currently, does anyone know any workarounds?
I went ahead and merged your request into an existing feedback request thread. Don’t forget to upvote there
Also here was a discussion about this topic as well with a potentially workaround listed Subtask Dependencies - #21 by Phil_Seeman
I think our “Add subtasks” rule action in Flowsana would be a great fit here - it can do exactly what you’re asking for here (something which the Asana “Add subtasks” rule action cannot).
