Briefly describe (1-2 sentences) the bug you’re experiencing:
Reccurring tasks not responding to rules
Steps to reproduce:
Add sections ToDo and Done in My Tasks (I’m guessing other projects behave the same, but I’ve seen it in My Tasks)
Make recurring task in section ToDo
Add rule to move completed tasks to section “Done”
Now the task gets moved to “Done” and the new occurence is created in the same section.
Even when I make another rule that tries to catch the new task being created and moving it to the right section, the rule seems to ignore the new task and it will always stay in Done.
Browser version:
Desktop App
What version of Asana are you using (Personal, Starter, Advanced, Enterprise, Enterprise+, Premium, Business or legacy Enterprise)?
Enterprise
@Jan-Rienk - I think this is less a bug and more a known design choice/issue: instances of recurring task do not trigger the “task added to this project/my tasks” rules as we might expect. There are a few request threads on this, including this one:
I agree that it really doesn’t compute for me why this trigger would not be met. I believe Flowsana does view these are newly created/added tasks if you happen to use it.
HI @Jan-Rienk sorry for the trouble. @Stephen_Li is correct, and this is a limitation rather than a bug.
At this time, rules will only work when you manually trigger them or if another rule triggers them. For example, when you mark a recurring task complete, Asana will automatically duplicate the task and add it to your My Tasks. If you have a rule stating “Task added to My Tasks → Action XYZ,” this action will not be triggered because:
You are not manually adding this task to your My Tasks
Another rule is not adding this task to your My Tasks; it is simply a task duplication.
Regarding the first part of your question, please note that every new task added to your My Tasks is automatically added to the “Recently Assigned” section, which is also expected product behavior.
You can adjust this via the Hacks tab of your profile settings to add a recurring task into the last section of your My Tasks instead of Recently Assigned . Therefore, you can place any desired section last to make sure the new tasks will land there, however, if your desired section is not placed last in your view, this won’t work.
Hi @Jan-Rienk, I completely understand your point, and appreciate your feedback. I have already filed a feedback report for this topic, but I’ll also move this thread to our Product Feedback section so other users can upvote this request.
@Vanessa_N I think the rule closing this had to do with the bug category this post used to live. So I opened it again. (And de-selected the solution as I don’t consider it solved)
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
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?
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.)
