I have My Tasks separated into Today, Recently Assigned, Upcoming, and Later. Up until yesterday, whenever I marked a recurring task as complete, the newly created task (for the next recurring date) would appear in Recently Assigned. That is what I expect and want to happen.
As of yesterday, that isn’t happening. Instead, the newly created task is appearing in whatever section the completed task was in. This happens on both desktop (Mac) and mobile (iOS app version 26.31.0). I’m not sure if I’m being clear so I recorded this happening on my screen, but I don’t see a way to upload a video file into the post. If the video would be helpful and there’s a way I can send it to you, let me know.
How do I get the tasks to show up in Recently Assigned again rather than in whatever section they were in when I completed them?
I too am expreiencing the same thing. It just started today. At the end of the day i look at my tasks grouped for “Tomorrow”. Some i don’t have to do so i mark them as complete and they normally would leave the “Tomorrow” and go under another grouping like “recently added” or “Upcoming” as I would need to look at them again in the future. But as of today the completed tasks leave the “Tomorrow” group and come back to that group with a future date (like a month or year away)? Why did it just start doing this?
Same issue here, and unfortunately it completely breaks the workflow I have set up
Tasks were originally moving back to the “default” or “special” section that was created by Asana when I first accessed My Tasks. Now tasks are being put into the same section that they’re completed in instead of being moved back to that default section.
Hi everyone! Thanks for raising this. The issue has been escalated internally and is now under review. We’ll provide updates as soon as we have them. Thank you.
Hi everyone, I reached out to Asana Support last week, but just found this forum thread now. I thought I’d share what I’ve learned so far.
From support agent Connie:
Our engineering team reviewed this behavior and confirmed that recurring tasks inheriting and remaining in their original section upon completion is actually the intended design in Asana.
Previously, a bug caused newly generated occurrences of recurring tasks to default back to Recently Assigned, regardless of where the original task was located. A fix was recently rolled out to resolve that bug so that recurring tasks properly maintain their assigned section when completed.
We completely understand how this change disrupts a workflow built around the previous behavior. If you’d prefer future task occurrences not to sit directly in your active today view, a common workaround is to place or complete the task within an Upcoming or custom section, or adjust the task’s section rules to fit your preferred daily sorting method.
Since there are no viable workarounds available (especially on mobile), I have asked Asana Support to reconsider this engineering decision, as it disrupts many workflows that I’ve been using for years (as I suspect for many of you here). I am still waiting for a response.
I would be happy with any way to still use my prior workflows, including:
Reverting the bugfix to restore previous behavior
Add a new Rule trigger so that users can customize what happens to a newly repopulated task
Adjust the Hack (in Settings), permitting users to specify exactly what section recurring tasks reappear in
My most recent update from Connie was last evening (who is still awaiting word from the engineering team). I will post again here should I learn more.
If so, is it understood how a highly disruptive workflow was implemented seemingly without notice?
Also, Connie’s recommendation “adjust the task’s section rules to fit your preferred daily sorting method” doesn’t make sense to me, since rules won’t fire on recurring tasks.
Wow. If this is a bug, it’s been in place for years. And I think it makes more sense than a task showing up again in the same section on My Tasks page anyway.
If they aren’t going to go back to the “bug” behavior, maybe they should at least create another hack option like the “Recurring tasks in the last section of My tasks” one, but have it cause things to float to the top.
This “bug” is the way my recurring tasks have behaved since I started using Asana… and that’s been years ago. The “fix” they’ve implemented requires significant changes to my workflow, including constantly moving tasks out of the “Today” section that should no longer be there. It’s turned my previously smooth workflow into a real pain point.
The behavior discussed here seems related to a previous discussion about differences in how recurring tasks behave in My Tasks versus Projects:
In short, it seems the behavior within My Tasks has now become the same as the behavior within Projects. Is this actually a configuration change tied to that — i.e., is this thread’s issue
a downstream effect of that same change?
If so, it would seem more natural for “recurring tasks” to also trigger rules — on that point, I’d suggest referring to this thread:
In any case, this feature’s configuration change is a combination of Asana’s strengths and weaknesses, so a simple fix seems unlikely — it will probably take some time to resolve. For the time being, perhaps it’s best to revert to the original settings while a better solution is worked out.
I’ve had recurring tasks set up in My Tasks in this same way since 2018. How is it possible that this was considered a bug. There a Hack in Settings that allows you to toggle on sending Recurring task to the last section of My Tasks. But this appears not to work either.
Agree that this “fix” has broken my workflow and is clogging my active “Today” list with recurring tasks for next week, next month, next year that I now need to remember to filter out (previously, it was a quick fix to move them out of “Recently Assigned” as needed).
It honestly just seems like some of the rules aren’t working… If I tick a task in “today” and the next time it’s to come up is next week, it shouldn’t be going back to the same spot in “today” - the rule doesn’t say to do that.
