The problem:
Weekly recurring tasks anchor to chosen weekdays, and monthly tasks can anchor to a specific calendar date (or nth weekday), so a one-off reschedule doesn’t disturb the series. Yearly recurrence has no such anchor: the next occurrence is simply computed from the task’s current due date when completed. Consequently, a one-time reschedule permanently re-anchors the entire series.
Example:
A task recurs yearly on January 1. In 2026 I push that occurrence to January 5 and complete it. The 2027 occurrence is now due January 5, and every future year inherits the drift, unless I remember to hand-correct the date each time. Annual obligations (renewals, filings, anniversaries) have a true fixed date that shouldn’t change because one year’s occurrence slipped.
Real-world impact:
This isn’t hypothetical: I’ve moved a whole category of my recurring work tasks out of Asana into another task manager specifically because of this. For date-critical annual items, I need to trust that the date I set is the date the task recurs; today only Weekly and Monthly recurrence earn that trust. I’d gladly bring those tasks back into Asana if Yearly recurrence held its anchor the same way.
Suggested solution:
Give Yearly the same treatment Weekly and Monthly received: let users pin the recurrence to a specific date (e.g. “every year on January 1”) stored in the rule, independent of any single occurrence’s due date. Rescheduling an occurrence would then defer only that occurrence, with the series snapping back to its anchored date, which matches the behavior users already get from the other recurrence types.