+ Add Question

Multi-year, month recurrences don't calcaulate correctly

DW

As many people have noticed, TD doesn't recognize the word year. The usual answer to "how do I schedule a task once a year" is "every mm/dd". But what if I have a task that needs to happen every *other* year? I can't say "every 2 years starting mm/dd". One workaround is to say "every 24 months starting mm/dd" but TD doesn't do the calculation the way you would expect. For example, when I enter "every 5 years starting 7/1/2012" into the web app and I complete the task, the next task is scheduled for 6/5/2017 rather than 7/1/2017. When a human says "n months from now", they typically mean "on the same day of the month, but increment the month number by n".

Am I wrong about this? Is there anyone reading this who would consider 7/1/2012 + 60 months = 6/5/2017 to be the right answer?

This would be a lot easier if you would support the word "year", but the same caveat applies to leap years, i.e., a human considers 7/1/2011 + 1 year = 7/1/2012, *not* 6/30/2012 (which would be 7/1/2011 + 365 days).

All responses

David Trey staff
Replied on Nov 28, 2012 - 09:16

Hello David,

Thank you for your feedback, we appreciate it and will consider adding more syntax options in the future.

Right now, if you type "month", Todoist will understand it as "30 days". The only workaround to set a bi-annual task would be to use the following formula:

every 730 days starting mm/dd

The only issue with this solution is that every leap year shifts the next occurrence one day back.


Best regards,
David

DW
David Wagner premium
Replied on Nov 28, 2012 - 09:32

It's not just a syntax option -- I could get around the syntax if the "month" interpretation were correct. The current interpretation of "month" is a bug, IMO.

David Trey staff
Replied on Nov 28, 2012 - 11:45

David,

We will consider correcting the handling of the "month" syntax (not make it a fixed 30 day span) and once we do, we could then add support for "year".


Best regards,
David

U
Unknown
Replied on Jul 18, 2013 - 18:49

Hi David Trey,

Any update on this fix? I agree completely that 1 month is not equal to 30 days; this is a serious bug.

David Trey staff
Replied on Jul 19, 2013 - 06:17

Hello Kirk,

We're sorry for the inconvenience, we'll surely look into it in future updates.


Best regards,
David