Tasks moving a day forward
I just started using Todoist a few days ago. And Gremlins have gotten hold of my account.
I set a task for Wed, logoff, login, and now it's due on Thurs. Reassign to Wed, logoff, login, and now it's due on Thurs. Rinse and repeat.
All of my tasks are doing this - shifting one day forward. Grr. I just manually transferred all of my tasks from RTM and am holding off on adding birthdays until this straightens out.
Help me Obi Won, you're my only hope.
Asked by Paula Londe on May 07, 2013 - 10:33
Obi Won is not available at the moment, but maybe I can help. :)
Is your PC set to the proper time zone? Are you using any handheld devices (iPhone, iPad, Android phone) to access your Todoist account? Are those devices set to the proper time zone? Have you added/changed any tasks on those devices? Have you traveled between time zones recently? Has Todoist asked about updating dates? Has the PC asked updating dates?
I know that I've a LOT of questions, but this usually leads to the solution. One last hint, please check that your PC is set not only to the proper time zone, but to the proper date as well (I, know, that it TOO obvious!).
My account was doing the same thing, and this post helped me - I had to make sure all the versions of the application were in the same time zone. I had changed the time zone via the Todoist Android app on a business trip because it prompted me to, and it also prompted me to change it back again when I returned, so I thought it was updated. I had never logged in and updated my timezone online, however (I mostly use the Android app, and sometimes the desktop client), and when I logged into the website to see if this was a known issue, it prompted me to change my timezone again, and then the issue was fixed. Do timezone settings really not sync across devices? And why would a one-hour time difference (I traveled between California and Colorado) bump tasks to the next day?
I'm glad I was able to find a way to fix the problem because it was a huge annoyance, but it still seems like there is a bug here to me.
Thanks for the help, Randy!