I experienced an issue in Oct 2024 that has now popped up again.
Here’s the link to the discussion Rule keeps moving task back to initial section - #57
In short: A rule is created to add a task to an additional project (Project B) when it is moved to a specific section in Project A or the due date is set. The rule now suddenly auto assigns a section when moved to Project B. The problem is that when I change the due date a second time, it moves it back into the specified section in Project B. This was not an issue before because specifying the section in Project B was never there. Is there any way to remove this?
The problem is the part where it says “Choose a column/section”, because it forces you to choose one, or it auto assigns. It used to not has this as a requirement.
(1)
Create a dropdown list custom field - you could call it “Added to project” or “Add automation run” for example - and only create one value for it - you could call that “Yes” or use a checkmark emoji. Then add an action to your rule to set that custom field to that value. Then add a condition to the rule “If [name of that custom field] is empty”. In this way, the rule won’t run again once it runs once. (You can hide this custom field as a column in the view - there’s no need for people to see it.)
(2)
You can avoid having to create and use the extra custom field by using our Flowsana integration; we have a “Due date is set” rule trigger which, unlike the Asana due date rule trigger, will only run when the due date is initially set - so the rule won’t fire when the due date is changed form one value to another.
The Due date is set because we have a master template project we duplicate from. Due dates come up later in the project so we want it to move there once a due date is set for specific tasks. I will chat to the team and see if this can be left out though.
When we duplicate from the Master Template project, there are already templated tasks and subtasks. The problem is that there isn’t a rule to automatically add the tasks in the Creative section, to the Creative project (the additional project). So there has to be a due date assigned or it has to be moved in order to trigger the rule. The problem is that the alternative solutions would mean someone manually adds it to the Creative Project, which leads to user errors. The easiest one is to trigger the rule once due dates are updated, but now it jumps around in the sections of the Creative Project whenever a change is made.
