We love the custom task types, but would REALLY love them if Rules could generate a custom task type as a subtask in the Create New… section (like you can generate Task/Subtask/Approval).
2 Likes
Thanks, @lpb.
You bet - @J-Niv, you can do this with our Flowsana rules. They won’t create the subtask with the custom type, but as soon as it gets created, our rule will convert it to the desired custom type. For example:
This example converts ALL new subtasks to the custom type “Bug Report”. If you only want to convert certain newly-created subtasks, just enter the appropriate Condition(s) that will uniquely identify those subtasks to convert.
This isn’t to take away from your request and your vote here; but it is a solution unless/until Asana provides the capability natively.
3 Likes
I think I’ve found a workaround. I created another project named “Conversion Space” with the custom task template I want to apply and the following rule:
Then, in main project rule creating the subtask, I set it to multihome the subtask into the Conversion Space project. When it’s done converting, it gets removed from the Conversion Space project and is left in the main project with the template applied, including the ability to write additional rules based on the custom task’s value.
It’s probably not always necessary to add the “check if task is approval” portion, but I was looking at potentially using this conversion project for multiple types of custom tasks in the future.
1 Like
Well done, @Leigh_Flynn!
If you do in fact use the project for multiple purposes, it might be better to bite the bullet and make some kind of single-select Action custom field to enumerate the supported actions all in one field so that you can reliably maintain and process all requests.
Thanks,
Larry
1 Like