I have a custom field called “progress” that helps me track progress with the task.
The rule that sets the field value of a new task to “unbegun” works very nicely.
The rule that sets the field to “complete” when the task is Marked Completed also works really well.
But any recurring task comes back into the project with “progress = complete”.
I thought a simple solution was going to be
When: Task is added to this project → Do this: Set Progress to Unbegun
or even
When: Task is added to this project → Check if: Progress is set to Complete → Do this: Set Progress to Unbegun
But neither have any effect.
Hoping you have some advice about how to get recurring tasks to be parsed by rules. Many thanks
The way the rules currently work, “new tasks duplicated by repeating actions” cannot use the trigger “When a task is added to a project.”
So, as an alternative, since “new tasks duplicated by repeating actions” are created in the topmost section of the list view (generally the “Untitled section”), by using “When-Task is moved to a section” in another rule, you can take some kind of action (such as setting a due date) on the “new tasks duplicated by repeating actions.”
I think what you’re saying is that you can manually run a rule since it won’t automatically run for a new task recurrence.
That’s maybe the only way, and I guess it could be seen as a workaround, but I think many would have already ruled this out as not enough of a workaround.
I think this is not a solution to the problem ““Task added to this project” Rule trigger isn’t met with repeating tasks” but an alternative (workaround).
If possible, it would be better to use “When-Task is added to this project” in “Duplicate task”.
Hi Everyone. I am looking for a way to have a reoccuring task stay under the section I created it under. Right now, I have sections based on Projects/Topics I have for work. I have a Daily Tasks Section, and the daily tasks are set up to repopulate everytime I click that it is finished, but with a due date for the next day. However, when it repopulates, it changes to the “recently assigned” section, not the Daily Tasks section. How can I fix this?
When a recurring task is completed, the assignee is automatically carried over to the new task. Has anyone found a way to create a rule that clears the assignee on the newly created recurring task?
I think adding your vote and voice here will help, as it would solve this specific problem and then some: Recurring Tasks to Trigger Rules
Your request is quite specific, so I’m not merging it. Would you be ok with me moving this topic to Tips and Tricks? Or would you like to keep this specific feedback?
FYI as @lpb says, unlike Asana, our Flowsana rules do trigger on a new instance of a recurring task, so you could use Flowsana to clear the assignee on said new instances.
(@Jan-Rienk I do think this topic should be merged, as enabling triggers on recurring tasks would definitely allow one to then clear the assignee.)
I’m experiencing a similar issue and it would really be helpful if recurring tasks could trigger rules.
I was wondering if you have tried a workaround using a “due date is approaching” rule? It should be triggered by the recurring duplicated tasks that is “added” automatically? Obviously, that will happen with a lag as it is only triggered at midnight I believe…
Confirmed that triggering on the Due Date Approach does work for this. Not limited to midnight because you can set the due date to a specific time of day and make the rule relative to that (e.g. 6 hours before).
We use the repeat function to manage re-capturing of repeat tasks so the assignee can avoid manual re-entry of the same task for the future period. However when the task is completed the data in our custom fields remains the same as Asana recognizes the task a duplicated rather than a newly added tasks and therefore we don’t have the ability to create rules to re-set the data in our custom fields at the point of duplication.
This rule would greatly benefit our users and reduce the amount of manual resetting they must do on custom fields after a task repeats. It would also mean that the dashboards and board views used by the teams management to monitor the progress and status of our tasks would be accurate and in real time
Thank you @Jan-Rienk
Yes I’d like a recurrence of a task to trigger a rule so that we can maintain custom field integrity based on our own Status custom field
