# Custom field conditions and subtask rules

**URL:** <https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471>\
**Category:** Asana In Practice\
**Tags:** custom-fields, subtasks, rules\
**Created:** [5 July 2022 14:29 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471 "2022-07-05T14:29:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon25517230](https://luna1.co/8d76cd.png) [@anon25517230](https://forum.asana.com/u/anon25517230)\
**Post date:** [5 July 2022 14:29 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471/1 "2022-07-05T14:29:01Z")

</div>

I’m creating an approval project that has a number of different stages of approvals from different individuals.

What I’d like to do is have the top-level task be the “project” (ex: Draft Approval) and the details and approval tasks be sub-tasks. This allows all the details to remain together.

My desire is for rules (at a simple level):

If subtask approval is approved and Custom Field = Status A (that’s set when it’s moved into a section) then move to next section. In that Next section, status would be updated to B and then a new approval task would be added.

From what I’m seeing, you can’t have a condition on an unchanged custom field only changed or cleared and you can’t run rules on sub tasks.

Does anyone have suggestions on how to automate this or am I stuck in manual turmoil of watching for approvals and changing the status?

---

<div class="post-metadata">

**Author:** ![Andrea\_Mayer](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/andrea_mayer/32/39226_2.png) [@Andrea\_Mayer](https://forum.asana.com/u/Andrea_Mayer)\
**Post date:** [5 July 2022 17:30 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471/2 "2022-07-05T17:30:45Z")

</div>

Hello @anon25517230, welcome to the Asana Community Forum 👋

The main task is it always assigned to the same person or reassigned as it moves along the stages? If so then automating it with rules would work.

Maybe this helps: [Approval Workflow - #2 by Andrea\_Mayer](https://forum.asana.com/t/approval-workflow/132144/2)

Rules for subtasks would be possible with [Flowsana](https://asana.com/de/apps/flowsana)

And here is the relevant feedback request thread for rules on subtasks: [Allow Rules for Subtasks](https://forum.asana.com/t/allow-rules-for-subtasks/71910)

---

<div class="post-metadata">

**Author:** ![anon25517230](https://luna1.co/8d76cd.png) [@anon25517230](https://forum.asana.com/u/anon25517230)\
**Post date:** [6 July 2022 15:16 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471/3 "2022-07-06T15:16:20Z")

</div>

So the current thought is the Main Task stays with one person.

The approval subtasks change depending on the section. So 4 different section and 4 different approvers.

Submit Form → Section A\Approver A → Section B\Approver B → etc

The issue I see (but verifying) with Flowsana is that they can’t do per section nor multiple conditions. So saying if subtask is completed move to section B, appears to move ALL subtasks completions to section B regardless of where it happens.

Thanks

---

<div class="post-metadata">

**Author:** ![Andrea\_Mayer](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/andrea_mayer/32/39226_2.png) [@Andrea\_Mayer](https://forum.asana.com/u/Andrea_Mayer)\
**Post date:** [6 July 2022 16:11 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471/4 "2022-07-06T16:11:30Z")

</div>

Oh okay I understand.

We are handling a similar process and atm, due to no rules on subtasks, we ask team members to update a custom field under the main task which then triggers another rule.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/system/32/276370_2.png) [@system](https://forum.asana.com/u/system)\
**Post date:** [30 May 2025 19:03 UTC](https://forum.asana.com/t/custom-field-conditions-and-subtask-rules/177471/6 "2025-05-30T19:03:53Z")

</div>

Closed on 30 May 2025 19:03 UTC


