Recurring task not appearing in Recently Assigned after completion

@Lauren_Finger1,

We know rules aren’t related to this issue because rules have never triggered when a new recurring task appears.

Thanks,

Larry

Ah! Thanks, Larry.

1 Like

Since the rule function is not executed for recurring tasks, a new task will be created in the previous section.

As an alternative, you can move tasks by making extensive use of due date change rules. For example, you can use triggers such as 3 days before, 1 week before, or 10 days before. However, you will need to wait one day for the rule to be executed.


This is slightly off-topic, but recently I’ve been using the “Scheduled time occurs” rule instead of recurring tasks.

This seems better for creating tasks like 9 AM every day or every Monday.
With recurring tasks, the next task isn’t issued until the previous one is completed, so recurring tasks that are forgotten can end up being forgotten in the distant past.

Alternatively, I frequently use follow-up tasks.

Hi,
In my environment it still works well.

The old behavior was definitely NOT a bug because they specifically had a hack for leaving it in the current section. In fact, leaving the setting as a hack was always the best solution so that users could decide what behavior to choose.

This change has broken my workflow also. And I wish that they would revert it.

The problem with this change is for anybody that uses My Tasks sections as workflow status indicator (todo, in-progress, blocked, etc) or for time indicator (today, upcoming, later, etc.), this change completely breaks the workflow. The new instance of a repeating task must not automatically stay in the last section because the meaning is wrong. It needs to go into a separate section so that it can be later assigned to the correct section.

PLEASE, revert this change!

8 Likes

This change has had a very negative impact on me as well, living in Japan.

I don’t speak English, so I never normally post in this global thread. This is my first time, but I’m translating carefully to write this message. It’s had such a huge impact on me that I really want you to change it back.

6 Likes

I think I’ve found a solution (that actually works better than rules). Not sure how long this has been an option but I found “Groups” in the My Task board. I set it to group by “Due Date” in Ascending Order and hid all empty groups. Now if I change the date, it automatically goes to the correct grouping. It may not be perfect if you had more complicated rules than Today, Tomorrow, Next Week but it solves my biggest headache.

1 Like

This is a massive issue for me too. I spent several days going back and forth with support, who apparently didn’t know about the change, and then I was told that it is “now working as intended”.

They then provided me with a ‘fix’ that didn’t work at all (setting a trigger to move tasks to the ‘new’ column on due date) - which demonstrates to me that they have no idea how people are using the boards.

This will be a deal breaker for me. I’ll give it a few weeks to see if there’s any change of messaging / plan to resolve it. If not, I’ll be cancelling my subscription. This is killing my workflow.

1 Like

I agree with the above - this new change has ruined the daily workflow experience for me. It’s changed a clean and efficient experience into something I would expect from a much more rudimentary platform. If it doesn’t change back I will also be likely to shift platforms because my workflow has been so disrupted. A real shame.

Hi all, reporting back. Since my original message from Connie at Asana Support last Fri Aug 14, my only messages from her since then have been “no update” updates.

Seeing the fervor of the conversation here on this forum page, I reached out to her again, to ensure that Asana staff are aware of the impact. Here was her response:

Thank you for following up and for bringing those forum posts to our attention.

I want to assure you that I’ve flagged these specific forum threads and user feedback directly to our engineering team so they are fully aware of the community’s response and impact. They are actively looking into this issue.

I’m continuing to monitor their progress closely and will reach out with an update as soon as I have news to share.

I appreciate your patience as we work through this. Please let me know if you have any questions in the meantime.

Since apparently Asana engineering is monitoring this thread, I encourage all interested parties to voice your opinions here. Asana is listening! :heart:

6 Likes

I’m also finding this new behavior very disruptive. Not happy.

2 Likes

Hi, @beyondthebeo

Using the grouping function is a very good idea.

For reference, I personally use filtering, sorting, and grouping together.

I find it hard to believe that a “bug” existed in the product for this long - so much so that a large portion of your users adjusted to it and began building workflows that depended on this functionality.

It would be great if we could get an option to return to the old behavior, or if there was a way to “opt in” to breaking changes like this. In any other software product, this would be gated behind a major version release and users would have to “opt in” to that behavior by downloading/installing the newer version.

I realize this is a SaaS platform so following SemVer is a pipe dream, but forcing breaking changes onto users is a sure-fire way to get people to stop using your product. Why would I spend time to fix my workflow if it can simply be disrupted/broken again in the future?

4 Likes

I am also very frustrated by this change. Please revert back to the old behaviors! The “recently assigned” section was an easy catch all for any new tasks created or recurring ones that I would later place in the correct section of my tasks. It’s so hard to go back and locate them all from within the sections they currently reside!

5 Likes

Time to start looking for a new project management solution. None of the possible explanations for this reflect a development process that I want to rely on for my business. “A core behavior had a bug in it for 8 years”, “We don’t care about breaking a core behavior for our users with no advanced notice and no workarounds”, “We shipped a bug 11 days ago and still haven’t fixed it”.

None of those possible explanations are reasonable.

3 Likes

To the best of my recollection, that was how Recently Assigned was supposed to function. I don’t want tasks I already completed “Today” repopulating same-day in my Today section.

1 Like

Great news from (Asana support) Connie!

Good news from engineering! After discussing with the team, they’ve decided to undo the recent change and keep the old behavior, so new recurring tasks will go back into the recently assigned section. This is expected to be live for users within the next couple of days.

Thanks to everyone here for speaking up, and to Asana for listening!

13 Likes

Welcome, @Chris_Slatt, and it appears there’s a better outcome expected now:

Larry

3 Likes

Great news. It is now back to working as it did here. I came back to the forum to double check that the fix is intentional and here to stay. Hooray!

1 Like