We recently started transitioning our task templates to Rules that auto-build tasks, and overall it’s been a big improvement for our team. It reduced manual steps and removed the need to copy task names into subtasks.
That said, we’ve run into a limitation around task types on subtasks. While we can create subtasks via Rules, the task type can’t be set at creation unless we add a separate action (this was not the case when we made the transition). If we are to use the separate action, it causes downstream issues (dependencies can’t be created between the tasks, tasks cannot be nested, etc.).
Task types are a key part of our workflow, especially since we rely heavily on approvals. We recently created a custom Approval task type that we’d love to use within these auto-build rules, but the current behavior makes it difficult to implement cleanly or at scale.
Has anyone found a good workaround for this, or is this a known limitation of Rules today? Would love to hear how other teams are handling task types + approvals in similar setups. Thanks in advance!
