Follow-up on: How to use approval subtask to trigger main task changes?

[lpb]

Note: Not a solution but marked as such to elevate a key reply

Yes, @Daniel_Kreiss, that’s a good point, though for those who can’t afford AI Studio or don’t want to use it when avoidable:

How to use approval subtask to trigger main task changes?

While this might be of value, it would let you see a difference between an Approval task that’s marked as Approved vs. Rejected; both will satisfy the “All subtasks complete” trigger. I think the only current way to manage this is to not use Approval subtasks but make your own single-select custom field for Approvals/Phases and rules around it, because then you don’t get into the situation of parent/subtask limitations with rules. (You can still add subtasks in actions if helpful, though, of co…

Please vote for this:

Using approval subtask to trigger main task changes

I have an approval subtask. When it is marked as approved, I want Asana to automatically change a custom field in the main task. Is there a way that I can do this with Asana’s current setup? The closest I’ve gotten is setting up the rule to check if subtasks are complete under a main task, but this does not fix the issues as a rejected approval is also a closed task. I realize this is not currently available in asana as a feature, but can we add this to the sprint if we think this is helping e…

Also, Flowsana.net (@Phil_Seeman) already does this.