Rule based on result of another rule not working

Briefly describe (1-2 sentences) the Bug you’re experiencing:
I have two boards. In the first board I have a rule to set a custom field to “Done” if the task is moved to certain columns.
On the second board I have a rule that says if the custom field is set to “Done” move the task to a specific column. This rule was setup first!
The tasks on the second board is a subset of the tasks on the first board.
The problem now is that the second rule which was set up later is not applied and the task is not moved to the column when the custom field is set to “Done”. First rule works as expected.
Any ideas how to get that working?


Hi @Holli,

The columns (also known as “sections” in Asana technical terminology) in the two projects are completely independent of each other - even if they have the same names in both projects, the two same-named columns are totally different objects under the hood and don’t know anything about each other, so to speak. So when the older rule fires and the task is thus moved to “Column X” in Project A, “Column X” in Project B (the project with the newer rule in it) is unrelated to “Column X” in Project A so the newer rule won’t be triggered. Hope that explanation makes sense!

Hi Phil, thanks a lot for the quick response, but maybe I wasn’t explaining the problem well enough.
The „connection“ is not a section (name), the connection is the value of a custom field on a task that lives in both boards.
So assuming there is a Board A and a Board B and a Task X that lives in both boards.
Board A has Rule A: if Task X is moved to certain column(s) change custom field value to „Done“.
Board B has Rule B: if Task X‘s custom value is changed to „Done“ move the task to a special column.

Rule A on Board A works. Rule B one Board B (created later) does not work if the custom field was set through Rule A. If the value is manually changed to „Done“ then Rule B works. However that is not the expected workflow.

So somehow it seems that a rule does not work if it‘s trigger is the result of another (previous) rule.

Does this make the use case clearer?

Thanks again!

Ah yes, OK.

Unfortunately you are correct - this is a limitation of Asana rules, as @Marie indicates here:

You can vote for a change in this limitation here:

Also, if you’re interested, Flowsana (which I’m the author of) does not have this same limitation. You can build the scenario you describe here using Flowsana’s If-Then Rules and it will work the way you want.

1 Like