Add a trigger for Rules that execute when TASK IS BLOCKED

It really helps to be able to automate workflow based on whether work is being blocked. I would argue it is also critical to know what work IS BLOCKED as well. In some cases users might not be able to accomplish a task that is upcoming, due or overdue because the dependency is blocking the task. In some of these instances the user might have influence on the dependency and could help get the task completed so their responsibility is unstuck and ready for action. Furthermore, I have seen where many users like to group tasks that are “pending” or “blocked” within they My Tasks or other Projects.

The ability to automate actions on tasks (like moving to a BLOCKED section) would be really nice. Because Rules don’t seem to execute in any particular order, the workflow attempted in the following post fails unfortunately - Allow user to define a specific order of rule execution - #5 by LEGGO

I think introducing some NOT condition triggers would really strengthen what users can automate. NOT blocked might be the most beneficial for me but I can see where others would also be useful (e.g. NOT in section or NOT with a due date)

1 Like

Hi @LEGGO, thanks for providing this feedback! I agree that this would be a helpful trigger to have with Rules.

Hopefully we will see this implemented in the future - I’ll keep you posted :slight_smile:


I could definitely use this to keep My Tasks organized and actionable!

1 Like

This would be extremely helpful in automating my workflow


How would this work, though? Rule triggers are based on changes in a task’s state; for example, the trigger “Task is no longer blocked” fires when a task’s dependency changes from incomplete to complete.

But “task is blocked” doesn’t involve any change in state; a dependent task starts out being blocked and continues to be so until it’s unblocked (per above). So I’m not sure how such a trigger could be implemented?

@Phil_Seeman perhaps the rule is triggered based on a start/due date but takes action differently depending on whether the task is blocked or not.

OK, fair enough, that makes sense!

1 Like