Rule to move tasks with no due date problem

I created a rule to move tasks with no due date to a certain section.

However, I am running into a problem where every new task I create is automatically being moved to this section immediately (even if I intended to add a due date, the task moves before I get the chance).

Is there any way around this?

@Darren_Yee - I believe this is expected behavior, since a task is considered “added to project” as soon as you start typing the title. Some ideas for solutions:

  • Use 2 task templates (1 w/ a due date, 1 without), downside is that you can’t just hit enter to create a new task
  • Invert your rule and add all new tasks to a section at the top called unscheduled (or something like that), then have your rule fire when you add a due date
  • Create a single-select custom field with one option (:white_check_mark:) called “Trigger” (or similar) and trigger your rule on when that field is changed. Then, create all your tasks and when you’re ready to trigger the rule, bulk-select them and set that field to trigger the rule for all selected tasks
3 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.