When I change the approval status of a task to “changes requested”, the dependent task incorrectly becomes unblocked and shows the approval task as having been completed.
This issue was brought up in 2020, and several others noted having similar issues, but the topic was closed in 2021 with no resolution. I was not allowed to create a topic linking the previous discussion.
I find it unexpected that if an approval task is marked rejected or has changes requested, the project proceeds as if it were approved.
As it is, the approval behaves exactly the same as checking a task complete. I’m left wondering what the purpose of that approval function in Asana is.
I had initially expect rejected approvals would hold up the project and return whatever task’s product was being reviewed to an unchecked state, but that functionality seems to be absent. It’s really just different colored icons that mean the same thing as task completed.
Approvals generally function better as subtasks of the work task they are approving. When seen in that context, which was how Asana envisioned them I believe, they can track multiple peoples’ approval, or multiple stages of approval, and it’s not consequential that they are seen as complete.
I don’t think they function well with dependencies, but anxious to hear back to my question above in:
Hi Larry, our developers have confirmed that this is the current behavior, and there’s no change planned in the short term. But they’ve noted all the feedback I forwarded. I’ve asked if they have any tips /workarounds to share and will let you know once I hear back
I really hope the dev team adds this feature, as it has the potential to be a great tool. As it is now, approvals cannot work with dependencies at all, and that drastically reduces any benefit to the approval feature. We will now have to create a custom column (with the approval/request changes/reject status) with rules to generate additional tasks/subtasks based on the column status.
Unfortunately, Even as subtasks, any dependencies relying upon the Approval become unlocked if “Request Changes” or “Rejected” are chosen. It seems that Approvals are non-compatible with dependencies, and unfortunately, that’s not how it works in the business world.
In our company, many documents and drawings are created and collected to become the Submittal. The CLIENT must Approve this submittal before any other actions can be taken. If the client requests changes or rejects the submittal outright, the team must go back to the drawing board and get the client what they want.
The Submittal Approval blocks the Approved Submittal Review, Permitting Application, and Update of the Customer Schedule.
To get around this lack of functionality, I’m creating a Custom Field called “Approval Status”. The options are “Approved”, “Request Changes” and “Rejected”. I’ve created a rule that creates a subtask if “Request Changes” or “Rejected” are chosen. I’m also changing any Approvals to regular tasks to protect the dependencies from inadvertently unlocking.
Is this the recommended course of action, or is there a better way to do this?