Briefly describe (1-2 sentences) the Bug you’re experiencing: “Task added to this project” Rule trigger isn’t met with repeating tasks. Although new tasks are created when tasks set to repeat are completed, if the “Task added to this project” trigger is used within a Rule on a project then the trigger is not met. This doesn’t seem correct.
Steps to reproduce: Create a Rule such as the following and you will find that the Custom Field isn’t set when a new tasks is created (added to the project) as a result of repeating task being completed.
Browser version: Google Chrome is up to date - Version 89.0.4389.114 (Official Build) (64-bit)
Upload screenshots below: Shown above.
More context: This is really valuable in circumstances where you might want to “reset” Custom Fields upon the completion of a repeating task.
Hi @LEGGO, thanks for reporting this! I’m investigating weather this is currently working as expected or is a bug. I’ll let you know as soon as I have more information.
Thanks @Emily_Roman. If it is expected behavior then I would love to understand what I am missing in regards to why a task created from a repeated completed task wouldn’t be seen as “added to a project” upon creation. If functionally it should be seen as any ordinary task added to a project, thus being a bug, then this could be a REALLY powerful benefit to repeated tasks once fixed.
Hi @LEGGO, I just received an update from our product team and they confirmed this is currently working as intended. As it stands, recurring tasks don’t trigger Rules. This works similar to the current limitation for rules that don’t trigger other rules! Our team is aware of this request and hopefully this is something we can implement in the future!
This topic was automatically closed 16 days after the last reply. New replies are no longer allowed.