It shows it ran 46 minutes ago so it appears to be firing.
Is there another rule (or person) causing another change to cancel out the result? Maybe pause other rules in this project and make sure the task isn’t multi-homed where another project’s rules could become involved.
Thanks,
Larry
Thanks for the reply!
So these are all of the rules I have setup:
The bottom 3 are all variatons on the original rule I’m trying to get working in this thread.
The first 2 move tasks into a “current” and “soon” section based on due date.
Does any of that sound like it would be conflicting to where the 3 new rules wouldn’t actually move anything, despite them running ok?
And I don’t know if it matters, but the “priority” field I’m basing off of is custom, not the default “high-medium-low” one that Asana has as an option.
Ok I realized that the above works when a task in “current” has its priority level set to not empty. Then the rule will trigger and pull it to the right section.
I want it to do that with tasks that get moved to the “current” section if they already have a priority set. So I adjusted the rule to be when priority is equal to those options and section is current, then move it. I’m not sure what will trigger it - I imagine it will happen when the tasks get moved to current? But tasks w/ priorities that are already in current at the adoption of the rule don’t appear to be moving. So I may have to move those to start before this will be all encompassing.
If any of that doesn’t sound right, let me know!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.