@Ericka_Paz I merged your post with the broader thread on this topic. Basically, approvals treat any status (other than the empty Approval Requested) as “complete”, which causes the behavior you’re noting. Make sure you give the thread a vote using the button near the title.
In the meantime, perhaps you could make use of the new custom task types where you can make specific “statuses” to complete/incomplete native statuses.
I never used approvals and recently I found a use-case where I thought they would be perfect, then I quickly found out/remembered why I never used them. Because requesting changes marks the task as complete. WHY. It would make much more sense if the assignee could see “changes requested” in their task list. Because of how subtask comments are separate from main task comments we never found it useful to have an approval subtask.
Would be great if there was an option to have changes requested NOT mark the task as complete. Also should note reject should not complete task as well.
Thanks for sharing your feedback with us!
This is now possible through Asana’s custom task types, which allow you to define task structures that better align with your team’s workflows. With this feature, you can create specific custom statuses and map them to Asana’s standard complete/incomplete states. This gives you more flexibility and the option to keep the task open when you request changes.
Feel free to reach out via the English Forum > Tips and Tricks category if you have any questions or need help setting it up! 
