I would like to be able to update the task description based on information from subtasks so that the main task has all relevant information prior to proceeding to the next phase.
A proposal is broken down into steps in subtasks, and when all information has been collated and subtasks are complete I would like to add all the information to the parent task using the info in subtasks via a rule so that I do not have to go and get the info from each subtask.
Unfortunately, asana rules only allow info to cascade down - subtasks can access info from parent tasks but not the other way around.
This alone would be a useful fix but something else that would be useful is if I could access information from subtasks that share a parent task.
Hi @WAAL , this sounds like a good use case for AI Studio. Have you tried it, starting with the trigger ‘when all subtasks are complete’ and the ‘Use AI’ as a variable in the action to ‘change the task description’?
In the instructions, clearly explain what information from the subtasks you want to extract and the format you want the output to be in the parent task’s (triggered task’s) description.
I have and the issue is when you want something done exactly the same every time it just doesn’t seem able to do it. There are occasional issues where it will do something else.
Additionally when I am part of an organization that is actively using AI, token limits are something that we need to be careful of - if we suddenly exceed the limit entire workflows collapse which we cannot have. As I expect this workflow to be quite heavily used and the action I want taken is relatively simple, AI would be unnecessarily overkill for this - The thing is if Asana AI can access that information, I don’t see why I can’t just be given access to it in the builder so that I can tell it exactly what I want it to do.
While I fully support AI use, this is a situation where AI would be completely unnecessary if I could access the info in the subtask in the builder.
Another such example is being unable to reference a Custom person-type field to set an assignee. This should be something trivial to do, but instead I am pushed to use AI for it.
Such limitations have forced me to rebuild certain flows externally in Zapier where I can reference virtually every field from the trigger.
I voted for this, @WAAL, and appreciate your reasoning.
Rules and variables should support reasonable cases like this.
I wouldn’t want to see AI Studio used as a justification for not implementing reasonably expected features. That would be a slippery slope. But until the feature is available, of course if it provides a workaround (maybe not in your case) that’s useful stopgap.