So glad to see multi-select field support in forms and rules, rules for adding subtasks, and dependencies added to task templates!
I’m hoping the same features that are available in Task Templates can be implemented in rules-created subtasks, namely: dependencies, and the ability to multi-home the subtask in another project.
This will allow us to make full use of forms; when a client submits a request using a form, we will be able to automatically add our workflow as subtasks based on the requirements they select in the Multi-select field. If a client selects “editing” and “translation”, we will be able to automatically add an “edit” subtask and a “translate” subtask, where the translation is blocked until editing is complete. We multi-home our subtasks so that we can track workload for each step.
If this can be implemented, we can have our team’s workflow virtually 100% automated!
It looks like we can now multi-home a subtask that is created via a Rule! Not sure when this was added. What I mean is, if you create a Rule where the action of that rule is to add subtask(s) to a task, then we can now have each of those subtask(s) also added to other project(s). I’m excited for this, as it’s been a feature of task-templates for a while!
Really hoping that we’re able to create dependencies through automation! At this point, you can make a secondary subtask dependent on a primary subtask, but there’s no way to make subtasks block the parent task. Seems like such a logical next step.