We’re trying to have all tasks assigned to me bundled into one project. However I also add items in this project manually and it causes a bit of a loop with “rule a”.
Here’s a couple suggestions for rule options that would fix this:
When: task is assigned to me
Check if: it already exists in “project A”
Do this: do not run “rule a”
“Rule a” moves tasks to a central project when they are assigned to me.
Here’s an alternative idea:
When: task is added to my tasks
check if: task is not added to project a
do: add to project a
This would allow it to run “rule a” if the task doesn’t exist in a specific project or only run the rule when the task doesn’t exist in a central project
How you ever tried setting up the rules in your ‘My Tasks’? With this, the tasks are definitely assigned to you, so you only need to set up a rule to ‘Add new tasks to Project A’. I haven’t tried this yet, but I think it will work. Let me know. Cheers.
It shouldn’t matter if the task is already in the project or not; there’s no need to account for that case in the rule specially; it will work either way.
That is where I tried to set up this rule and it messes up because if it is already in “project A” in whatever section I added it to, it then will move it to a different section.
That’s true (I didn’t know it was an issue because you hadn’t mentioned that in your original post).
One workaround is to have a rule in the project that sets a single-select custom field In Project to Yes (its only value) when a task is added to that project, then in your My Tasks rule, add a Check if In Project isn’t Yes. If you remove the task from the project you’d want to unset the field to be thorough.